2.3.5 Update Broke Vanilla Integration
Best Answer christopher_a , 23 November 2012 - 12:42 PM
Thanks, that helped point me towards the .htaccess file, but not actually a deletion issue. I found on the Vanilla community forums that there was an Apache update for BlueHost that requires a change in the .htaccess file in the Vanilla install directory:
# RewriteBase /
should be edited to
# RewriteBase /forum
I'm not with Bluehost, but editing the .htaccess file fixed this on my host, so perhaps they too rolled out a similar update which requires a more direct path?
However I updated Vanilla before the v2.3.5 update was available and everything was working smoothly, so either updating to v2.3.5 freaked it out, my webhost's Apache update changed something, or there's something else I broke somewhere. Go to the full post
#1
Posted 04 November 2012 - 12:49 AM
#2
Posted 04 November 2012 - 01:35 AM
If not, please let us know.
#3
Posted 05 November 2012 - 03:16 AM
After I tried switching permalinks from 'post name' back to 'default' which directs all forum thread links to the default Wordpress posts page. Changed it back, and threads = 404 again.
#4
Posted 08 November 2012 - 04:10 AM
#5
Posted 08 November 2012 - 04:13 AM
I've not used Vanilla before so I'm just gonna suggest some things which instantly come to mind, they might not be relevant to this situation, but might make sense somewhere etc.
Is everything published, nothing holding as a draft/preview anywhere? No slugs changed on any of the pages? In the admin area, can you see the content which is bringing up the 404 anywhere?
#6
Posted 20 November 2012 - 06:26 PM
There is nothing saved as a draft/preview in Wordpress.
#7
Posted 20 November 2012 - 10:04 PM
Contact your host and ask them for a restoration of your server from before you made the change. It's really not related to PL's update.
#8
Posted 23 November 2012 - 12:42 PM Best Answer
should be edited to
I'm not with Bluehost, but editing the .htaccess file fixed this on my host, so perhaps they too rolled out a similar update which requires a more direct path?
However I updated Vanilla before the v2.3.5 update was available and everything was working smoothly, so either updating to v2.3.5 freaked it out, my webhost's Apache update changed something, or there's something else I broke somewhere.
#9
Posted 23 November 2012 - 01:44 PM
Is this issue now resolved ?
#10
Posted 30 January 2013 - 12:20 AM
I had the same problem, followed the instruction on Vanilla forum to fix the issue by changing some details on the .htacces file but i was unsuccessful. I have to reinstall the forum and start afresh.
#11
Posted 30 January 2013 - 12:35 AM
Carl,
Thank you for letting us know.
If you need additional assistance, please open a new topic.


This topic is locked








