Hi,
I'm new, and french, so, excuse me for my bad english.
URL to your eFiction: http://padme.a.free.fr/eFiction31/
Version of eFiction: 3.1 (new install, not upgrade)
Have you bridged eFiction, if so with what?: I don't know what Bridge is, so I guess the answer is "no".
Version of PHP: 4.4.2 or 5.1 (I don't know which one. It has been difficult to find the information on my hoster)
Version of MySQL: 5.0.23
Have you searched for your problem:Yes, I checked all threads about categories.
If so, what terms did you try: Remove skins, checked some files, and re-install all the script. I don't remember all the things that I tried.
State the nature of your problem: Categories page is empty. I have 4 categories, and we can see them in the block here :
http://padme.a.free.fr/eFiction31/index.php
But not on this page :
http://padme.a.free.fr/eFiction31/browse.php?type=categories
Do you have a test account for us?No, but I can If you need.
Thanks for your help.
Does that skin have a categories.tpl file? If it does, try deleting it off of your remote server and on your local computer.
Whoever said nothing is impossible never tried slamming a revolving door.
url: https://www.potionsandsnitches.org/fanfiction
php: 7.4.33 msql: 5.6.51-community GPL
efic version: 3.5.5 latest patches: yes
bridges: none mods: challenges, tracker, story end, beta, word
No, it doesn't have.
Please see this thread.
You cannot use the word "type" as the name of a classification type. It conflicts with other settings in the script.
I changed it. But I had the problem before I added the classification "type".
And it doesn't changed anything. The categories page still won't show.
Turn debug on in your settings.
Done.
And now ?
It's a bug in the script when you've got columns set to 1. Set your columns setting to 2 or more for now. It'll be fixed in the next update.
It works !
Thanks ! 😀
I'm sorry if this isn't allowed, but I thought that for the convenience and sanity of future members with this problem, I'd add this little note...
I'm using 3.0, and had this problem. Fixing the number of columns still works.
I'm sorry if this isn't allowed, but I thought that for the convenience and sanity of future members with this problem, I'd add this little note...
I'm using 3.0, and had this problem. Fixing the number of columns still works.
Try upgrading to the latest 3.1.
It's not fixed in 3.1. It'll be fixed in 3.1.1 which should be coming this weekend.
