An Alternative to Efiction

@jimmi ah i see. Well it is an old script it still works though. Its just a date issue.

Those are time related fields in efiction:

fanfiction_authors date

fanfiction_log log_timestamp

fanfiction_comments time

fanfiction_reviews date

fanfiction_stories date

fanfiction_stories updated

fanfiction_news time

fanfiction_poll poll_start

fanfiction_poll poll_end

All those fields have to be numbers in 3.5.6.   The same steps are used in update:

- creating new field f.e. date_tmp that is integer

- copy and converting string date field with SET `date_tmp` = UNIX_TIMESTAMP( `date` )

At this point you should have string date and integer date in your table.

- changing original field to integer - and this fails in some case, no idea why

- copying date_tmp to date field and remove tmp field.

So my advise:

- copy fanfiction stories table from backup

- go to phpmyadmin and change default value for fields date and updated from value to none

- add date_tmp and updated_tmp fields 

- run update script (or continue manually)

It is important to have those fields as integer, there will be new version that depends on this. 

I currently don't have anything in these for some of them others I have a string of 0000 or one long number 1709531826 and in others I have years 2013.

fanfiction_comments time

fanfiction_reviews date

fanfiction_poll poll_start

fanfiction_poll poll_end

@jimmi Question if this was from a new install with no old database info why is the date like this? 01/01/70  It was news I recently posted. time stamp looks like this? 0000-00-00 00:00:00

@marcy

Thanks, I will check if I changed the installation table and test this again.  

This is correct: 1709531826

to display/check readable time use https://www.epochconverter.com/

Everything looks fine in my new install except two areas

Log ip has this 1756211727 and log timestamp has this 0000-00-00 00:00:00

News Time is also like this: 0000-00-00 00:00:00

Should they not be zeros? @jimmi 

I see what you mean about the date turning to zeros when converted by the server. Its okay to do it manually right? For some reason most dates were stripped leaving only the year when I upgraded

Picture here

I changed the second row manually

@marci give me time until this weekend. I will go field after field to check everything.  But write me your database server (it can be seen in phpmyadmin on the right side - MySQL vs mariadb or version f.e 8 or 10 etc). 

True is that I added new fields one after one to update the file...  and updating always worked for me, so I will need to add more checks.  This is a bit out of my league, but one should still learn. 

I can simulate your troubles with PHP 5 and older MySQL 5.6,  it is weird.  But I know where to look to fix this.  

PS. Do you somehow mark this topic only for users? I don't see it fully without login in and using CTRL-f5 to clear the browser cache. My topic about TinyMCE is visible normally. 

I login to post, but that's about it. I don't have admin privilege's to mark topics only for users. I assume for admin did that. I'm just a member here.

@marci I found the problem and I fixed the installation.  Database for clean install should be correct now (tables are on 2 places, I will know this in future 🙂 )

For testing, I put the new release here: 

https://github.com/e107-eFiction/efiction-3.5.6

By the way, my provider started to warn that PHP 8.1 is already outdated and we should move to PHP 8.2. It is a nightmare.  

I fixed these two today. The new install i fixed the date for the news so its correct now.

https://simplyjamesmcavoy.com/fiction/

And for this one all the story dates were 1970 so I updated them to the correct date using the tool you gave me.

I had to change one table for datetime to INT, but it done. I don't remember which table it was. Sadly.

https://simplyelijahwood.com/fiction/browse.php?type=titles

I have two others at 3.5.5, but i haven't touched them yet. The ones I couldn't port over to 3.5.6

Posted by: @marcy

↑

I have two others at 3.5.5, but I haven't touched them yet. The ones I couldn't port over to 3.5.6

I found something.

It is not tested, but I posted it on github - file update.php now should run the update database for the older 3.x version  - not tested

If you use 3.5.5 database and you don't have poll block installed, just delete related parts from the update file. In PHP 8 it ended with an error if the table doesn't exist. I didn't know that I needed to do this in the block update part.