The requested URL /symphony/publish/messages/ was not found on this server.
This is an open discussion with 12 replies, filed under Troubleshooting.
Search
I’m guessing your /symphony/.htaccess is bad/missing, or rewrite is otherwsie not working.
Yeah there is no .htaccess - that’s odd, why would that happen?
Just been told that the php was 5.1.6 - doh!
Have you just updated? When you update the new /symphony/ folder won’t have an .htaccess file inside it, since this is generated when you install Symphony for the first time. The README instructs you to copy this file elsewhere, upgrade, then copy it back.
Yeah it was a straight installation of 2.0.3 - do I need to install 2.0.2 first and then update to 2.0.3?
If you have done a clean install from scratch then the .htaccess will be created during the install procedure. If you had a previous version installed originally and then you have overwritten the /symphony folder when upgrading to 2.0.3, you should have copied the .htaccess from this folder first.
If the latter, and you did not back up the .htaccess file, you should do another clean install of 2.0.3 from scratch on a test server, and copy that .htaccess into your actual build.
Well I have a fresh slate to work with.
So am I ok to install 2.0.3 straight onto it?
Ok, I have run a new install.
And first of all it told me my workspace had no write permissions, and then symphony folder. So once I gave them 777 and then it installed. Gave me the login screen. And now it is saying this:
The requested URL /symphony/publish/articles/ was not found on this server.
The symphony folder has 777 permissions, it also does not have a .htaccess file again. So I tried to upload one from another fresh 2.0.3 installation and it doesn’t allow it to be copied, it says Permission denied.
Is Apache configured with mod_rewrite?. No .htaccess file would be the issue then.
Well the client insists that mod_rewrite is installed.
Hi NickToye,
I was having the same issues with the mod_rewrite not working on my local test server (WAMP + Vista) despite it being enabled. Fresh install also.
For me, fixing it involved placing the “AllowOverride All” command directly into the apache httpd.conf file. Without that command it didn’t work, even though the default apache command was set to this value.
example:
#LOCAL DOMAIN NAME ################ <VirtualHost *> ServerName yourdomain:80 DocumentRoot P:/drive-location-for-html-files <Directory "P:/drive-location-for-html-files"> AllowOverride All </Directory> </VirtualHost>
What does that mean?