Jump to content

DemonGoddess

Admin
  • Posts

    44,503
  • Joined

  • Last visited

  • Days Won

    217

Everything posted by DemonGoddess

  1. to fix that, set your browser to utf8 for encoding for now. I have to convert the db to that encoding.
  2. It is all being addressed. As I said before, just to get the chapters to display AT ALL took a combined 30 man hours for manta and I, in one day. yesterday, we both opted to give our weary eyes a much needed break. Today, AFTER work, I've got some things I'll look at, and show manta before I even think about going live. Remember, she's the primary coder for a REASON. Just as I'm the primary on database, for a REASON. That's where our strengths lie. Hers in code, and mine in overall db stuff. Which is why BEFORE she does something to the db, we talk first, just as BEFORE I do anything in code, we talk first.
  3. Given that between manta and I, we spent over 30 hours COMBINED working on getting the chapter data to display, you also have to understand that the finetuning will come probably later tonight or tomorrow. The priority yesterday was to get the chapter data to display.
  4. @Mira-Claude Thank you for the kind words!
  5. Hi there, I put numbers next to your concerns, so I can address them. 1. The odd characters are from the database language upgrade, which means that the database is now utf-8 for charset. This means I have to convert each and every table from latin1_swedish (the old charset from earlier versions of mysql) to utf-8. In the meantime, you can easily fix this by selecting the character set within your browser. Set it to utf8 and the odd images will disappear. 2. Give me links to some of the truncated ones, and I'll have a quick look. Chances are, that this is also related to the charset change, which is easily fixed with the rich text editor. These are actually things we DO need to know, as you've detailed it, so I know what it is that's happening. That's very helpful
  6. Yesterday, the priority was to get the chapter data to display at all. That's working now. Sure, I understand it's annoying not having "next" and other nav options, but that's something we'll take care of probably tomorrow after our eyeballs get a chance to get rested. Understand that combined, you're looking at over 30 man hours yesterday.
  7. Yesterday, the priority was to get the chapter data to display at all. That's working now. Sure, I understand it's annoying not having "next", but that's something we'll take care of probably tomorrow after our eyeballs get a chance to get rested.
  8. Yesterday the priority was to get the chapter data to display. There is a menu to the left, which displays chapters in sequence.
  9. Here's the situation: Manta had to rewrite the script which displayed the chapters. It's been a very long day for us both, so yes, we also know that you cannot review in the new script yet. She'll be adding that tomorrow.
  10. issues are fixed. review option will be fixed tomorrow
  11. only until tomorrow. The important thing tonight was to get the chapter data to display
  12. Manta is doing some fine tuning before she goes live right now
  13. I've made many, many posts about the white page o' doom thing already today. Yes, we are certainly aware of it. Yes, we are working on it, and yes, we're making progress. We're almost there now.
  14. it's not a DNS or page load issue, it's an outdated script issue.
  15. It's actually the file which loaded the chapter data for reading which was the issue. Manta is almost done rewriting it. It couldn't be patched to make it work, had to be rewritten instead.
  16. Please read the many posts I've already made about this. yes, we are aware of it. yes, we are working on it. (12 hours straight now), and YES, we're making progress!
  17. The login is a separate issue from the white page of doom. Being told to login again, tells me you've logged in using the center boxes. Use the boxes at the upper right corner, and you won't keep getting told to login in again. As to the white pages, that's something we are working on.
  18. Hi there, We are aware of the issue, and have been working on this since 8 am my time (it's now 5 pm). Still working on it.
  19. @TheSublimerOne Thanks! Needed that giggle!
  20. @Lerianis Appreciate the sentiment about the site. We've been working on this for several hours now, hope to have this resolved shortly.
  21. @DaFossil Thanks! Appreciate that! @wrightmother As I've already mentioned, we are working on the issue.
  22. and we are still working on it
  23. wait until we fix the newly uncovered deprecated code snippets. we are working on it. We are aware of the issue.
  24. wait until we fix the newly uncovered deprecated code snippets. we are working on it. We are aware of the issue.
  25. you don't have a forum login, so the forum assigns "Guest" to the front of your post.
×
×
  • Create New...