URL to your eFiction:
http://always-fanfic.net/eFiction/
Version of eFiction:
1.1 to 3.0.2
Have you bridged eFiction, if so with what?: NO
Version of PHP: 4.3.10
Version of MySQL: MySQL 4.0.22
Have you searched for your problem: (yes)
If so, what terms did you try:
stories submission taaking too long, stories, stories path
Have you looked at the FAQs:
Yes
State the nature of your problem: Copy and paste any errors you are receiving.
Well this is my second post, see below. I read somewhere that if the problems changes to start a different post to address that. I went back and restored my database and went back to 1.1. Then I reuploaded 3.02 and once I got to step 3, where it asks for stories path/ Well its saved to mysql. But its taking forever after I clicked submit and its not going to the next step,. Its still showing the busy sign now, is that okay? It shouldbt be taking this long should it?
Does it have to do with my server or me having too much stuff in my database? Cause currently I have my old storyline and then the fiction(1.1?) and then the current one with the ff prefix. Can I get rid of the old tables? here's the listing with the tables that has the most, please help lol. I dont knwo what else to do, I thought I was finally on the right path and then this happened.
tables:
fanfiction_authors
Browse: (0 Rows) fanfiction_blocks
Browse: (0 Rows) fanfiction_categories
Browse: (0 Rows) fanfiction_characters
Browse: (0 Rows) fanfiction_comments
Browse: (0 Rows) fanfiction_favauth
Browse: (0 Rows) fanfiction_favstor
Browse: (0 Rows) fanfiction_genres
Browse: (0 Rows) fanfiction_messages
Browse: (0 Rows) fanfiction_news
Browse: (0 Rows) fanfiction_ratings
Browse: (0 Rows) fanfiction_reviews
Browse: (1 Rows) fanfiction_settings
Browse: (0 Rows) fanfiction_stories
Browse: (0 Rows) fanfiction_warnings
Browse: (12 Rows) ff_fanfiction_authorfields
Browse: (0 Rows) ff_fanfiction_authorinfo
Browse: (1 Rows) ff_fanfiction_authorprefs
Browse: (268 Rows) ff_fanfiction_authors
Browse: (9 Rows) ff_fanfiction_blocks
Browse: (26 Rows) ff_fanfiction_categories
Browse: (0 Rows) ff_fanfiction_chapters
Browse: (160 Rows) ff_fanfiction_characters
Browse: (0 Rows) ff_fanfiction_classes
Browse: (0 Rows) ff_fanfiction_classtypes
Browse: (0 Rows) ff_fanfiction_codeblocks
Browse: (0 Rows) ff_fanfiction_comments
Browse: (139 Rows) ff_fanfiction_favauth
Browse: (0 Rows) ff_fanfiction_favorites
Browse: (391 Rows) ff_fanfiction_favstor
Browse: (8 Rows) ff_fanfiction_genres
Browse: (0 Rows) ff_fanfiction_inseries
Browse: (0 Rows) ff_fanfiction_log
Browse: (9 Rows) ff_fanfiction_messages
Browse: (1 Rows) ff_fanfiction_news
Browse: (26 Rows) ff_fanfiction_pagelinks
Browse: (76 Rows) ff_fanfiction_panels
Browse: (3 Rows) ff_fanfiction_ratings
Browse: (1572 Rows) ff_fanfiction_reviews
Browse: (0 Rows) ff_fanfiction_series
Browse: (1 Rows) ff_fanfiction_settings
Browse: (1856 Rows) ff_fanfiction_stories (41.4mb)
Browse: (5 Rows) ff_fanfiction_warnings
Browse: (1 Rows) settingsfanfiction_settings
Browse: (11 Rows) sl18_category
Browse: (1251 Rows) sl18_chapters (29.3mb)
Browse: (0 Rows) sl18_news
Browse: (508 Rows) sl18_rate
Browse: (344 Rows) sl18_review
Browse: (618 Rows) sl18_stories
Browse: (22 Rows) sl18_subcategory
Browse: (114 Rows) sl18_users
I think your server is down. Whether or not the update script caused it I can't say. If you got most of the way through the update before, I'd say probably not. As for tables you can get rid of. I'm not sure you restored your database back to 1.1 completely. Some of the tables in that list are 3.0 tables that weren't in 1.1. You also seem to have some tables with no prefix and some with a prefix of "ff_"
You're right, tammy my server is down. I tried connecting via ftp and it wouldnt work.
As for my tables, well I went back and did a new installation with 3.02 and I got it installed sucessfully. So what i did was go back to 1.1 and then did upgrade with 3.02 but this time with the same prefix of ff so it all my tabels worked.
SO the ff is 3.02 and the rest are old but I'm afraid of what to delete and not too. Well I'll contact my host and see what the issue is, just when I thought I'd finally gotten this right.
Ok.
Bump. Is this resolved?
Marking as closed.
