Jump to content

Click Here!

DemonGoddess

Admin
  • Posts

    44,481
  • Joined

  • Last visited

  • Days Won

    204

Everything posted by DemonGoddess

  1. resent. It's coming from technicalsupport@adult-fanfiction.org
  2. Did you check your spam folder? The mail I sent to you didn't get returned, so it went somewhere, and the spam folder is the most likely culprit.
  3. you're inputting your email address, in the box at the upper right corner, and your password as I sent it to you? The password field is case sensitive, so you do have to be careful with that.
  4. Archive is out of read only mode Subdomains converted: Sunday - 2-7 anime anime2 hp ne original Wednesday - 2-10 bleach books buffy I'm a third of the way there!
  5. With that res? That's standard for a tablet.
  6. I'll be setting the archive to read only in roughly 30 minutes
  7. Okay, going by the res, I thought I'd try something on one of the tablets here. We do not currently have a selectable mobile skin, so this actually won't be addressed until we get to that point. Before we do that, we do have other coding that we have to do first.
  8. Speaking of which, I'll be turning it read only in two to three hours.
  9. I'll check with manta about perhaps an addition to the css file, to make the background of "located with" a tad darker so it jumps out from the list. I'm not seeing anything in the css to actually do that formatting at present.
  10. @AlfonsoLing You need to be certain you logged in using the boxes at the upper right corner, NOT the center boxes.
  11. That's only IF you're making it zoom in a lot, or working in a tiny window. Normal settings there is no issue.
  12. thank you! See, I've had suggested in past that we make an app, but you know, the forum does it with a SKIN. Given that we have a broad base of users, most of whom don't actually USE mobile devices to do this, I think a skin will be our best option for the archive as well.
  13. @Inked_4_Life That makes sense. So, to actually fix the issue for you, is going to take developing a mobile skin. Those do better with more basic fonts, yes?
  14. I managed to fix a good chunk, but the format that makes for the extra line after has extra spaces in it, varying in length for this for instance. So, a simple query won't remove those. However, opening the chapter in the rte and then deleting the extra line will.
  15. @Lucy In the future, we will have selectable skins, including the old and (IMO) very ugly and dark plum/purple monstrosity. Sorry, but that killed these older eyes. The darker it is, the harder it is for many of us to see, well, anything. I'd rather work in an environment doesn't trigger a migraine after ten minutes due to eyestrain. However, that time is not yet. We still have other fish to fry, and all of it has to do with FUNCTION. Like I've said many times, function FIRST. I can sit there and make all kinds of color changes, but if things still arent' working right? What is the point? It's still broken. @linked_4_life Thank you! What device are you reading on where you're getting smashing? There are things we'll have to address once we actually get to selectable skins, for things such as mobile devices, as they handle display formatting very differently from a desktop. Now, we've tried to make it as friendly as possible for it without making that additional skin yet, but, there are definite issues in a desktop skin using a mobile device. I think it may actually be a font choice that'll help more with that. But not sure, yet.
  16. I just tried logging in and out as you, and was able to successfully. Emailed you with further instructions.
  17. Latest listing needs some form of division between the stories I think, yes? Is that what you're looking at?
  18. The links you save are the browser bar. The actual url. CL is correct. You can NAME your bookmarks.
  19. I was able to zoom to 250% before anything odd happened. I also shrunk my browser window to approx 1/8 of my monitor, before any oddness happened. We're still tinkering with it though, to keep it from happening at all. As to whether or not we pay attention to users, manta2g and I discuss NIGHTLY different suggestions and whatnot. For example, as a result of what was said about a complete zero out of the ratings, manta has decided to go about it differently. Yes, there will be a zero of actual number of ratings at first, BUT, all stories will convert to the new script and tables with a good rating. The ratings will adjust organically as the stories get rated by the readers in the new system. Avelynn, among others, commented on the missing contrast of the chapter read area, in that it was the same color as the sidebar. That was adjusted yesterday. As I stated earlier, however, overall cosmetics (such as quick buttons for convenience and that sort of thing) are the last thing on a long list of things to do with this. Everything has to work FIRST before adding extra "bells and whistles". There are some things that flat out will not happen, such as the title of an individual story showing in the address bar. To accomplish that, means we step backwards and decentralize again. Centralizing the bulk of the scripts makes for a healthier archive. Things we got away with for years in script operations, haven't been supported by the language cores for quite a few years. We got LUCKY that we didn't have worse issues than 1 day of white screen because of that. Understand that in the old code, there are STILL parts which are in php2, much in php3, and some in php4. PHP is up to version 7, so the code HAS to be brought up to date to function properly. The character set conversion is also one of those things that HAS to be done. I've had to modify my approach slightly to account for database n00bs who were working in it before me, and "playing" with character sets. This SHOULD have been a straightforward conversion. If using multiple character sets hadn't happened, it WOULD have been a straightforward conversion. When these people decided to go back to the default character set from whatever it was they used before? They did not convert the actual data, simply the table properties. That doesn't work. To date, I've found at least SEVEN alternate character sets from the default, that were used between 2005 and 2006. I'm sure there are more. After I'm done with all of this? There will be only one character set, which is as it should be. Having all those different character sets in inserted data also causes database instability. By converting to what MySQL NOW requires for default, the database is stabilized.
  20. Okay, putting up a schedule for the next time. I'll be setting the archive portion of the site to read only access at approximately 5 pm on Wednesday, February 10. I'll have it set back to normal access by 10 pm of the same day. Times are EST. The table sets and associated subcategories I'll be working in: bleach books buffy cartoon celeb comics ff When I get to the final phase, where the conversion has been checked and I'm ready to switch tables, I do delete the old table and rename the new converted ones. This takes approximately 3 to 5 minutes altogether, where you won't see any data AT ALL in the subdomain where I'm doing this. In other words, all blank pages, not the white page of doom, but there is no data to draw FROM while I do this last part. If you do see that, be patient, it'll be back up within a few minutes. Each table set takes a minimum of 45 minutes to convert and then check, so I might not get all the ones listed above done. Of course, the 45 minutes is based on the last set of tables I did, where I ran in to issues and had to come up with fixes. So, it could very well take less time this time around. I won't know until I actually do it. Now that I know for certain the oddball side effects that this conversion causes, I also know what to do to fix it all before I even make the tables live. That will certainly speed it up.
  21. Chapter nav is to the left, in order. So, if you bookmark on chapter 30, and go back to read, edit your bookmark to reflect the latest chapter you stopped at.
  22. Personally, I think the cat pokes are funny. That's the whole POINT of them though, really. To be funny.
  23. To do what you want with the title in the browser bar would mean taking a step back and decentralizing the code. We're working on getting AWAY from that.
  24. It's definitely possible, it's just a color setting in the stylesheet for that division. As I said, there are definite tweaks to be made on that end. But, right now, the code and whether or not it works, and the database and whether or not it's stable, are the priorities. Function first!
  25. First of all, the colors can be adjusted in the style sheet. I expect there will be further tweaking of it. As to the ratings, while we'd like to maintain them, it's not possible. Still looking at ways to get the aggregate exported and then imported in to a new table though. Just saying that it's not likely at this point in time to be able to do it. Although I'll never say never on that, because I thought I couldn't fix the extra lines after the database character conversion and was able to anyway. Just remember, all of this, this rewrite is a complete work in progress. So there are many things that will be changing. As to the NEED for any kind of change? It was definitely there. The scripting was incompatible to newer language cores, as we saw when I attempted to update to php 5.4.x. The database language core had a change in character set, which is what going read only for a limited time is about. I have to convert the text data from one character set to another. Further, without doing this conversion, and with the updates to language cores, it made the likelihood of a major database crash inevitable. So there are things that must be done, period. I'm not talking about cosmetics in this part either. Cosmetics are not a primary concern for me at this point in time. Integrity of the database, STABILITY of the database is what I'm working on, and is what my number one priority is at the moment. Once I have that taken care of, then other things can be focused on. manta2g does the coding. She is centralizing most everything, which is a GOOD thing. She is also making it so any of the archive scripting is compliant several versions AHEAD of the php version we're currently running. It makes the site run more efficiently. Again, the mechanics and stability are also HER priority at this point in time. Cosmetics are always the very last thing.
×
×
  • Create New...