12 replies to this topic

[SuperGait]

Als ik een template, snippet of chunk save krijg ik de volgende foutmelding:

"You don't have permission to access /concept/manager/index.php on this server."

Ik heb al van alles geprobeerd, maar ik kom er niet uit. Opnieuw installeren helpt niet. Misschien ligt het eraan dat ik hem in een subdir installeer?
Het meest voor de hand liggende, ook schrijfrechten voor de hele wereld aan index.php geven hielp niet.
Heeft iemand een idee om me verder te helpen?
alvast bedankt!

Edited by SuperGait, 18 July 2010 - 12:23 PM.

[Ralph]

This definitely sounds like a permissions or .htaccess problem... Make sure the .htaccess within the /manager directory only contains RewriteEngine off and nothing else...


Dit klinkt zeker als een of machtigingen. .htaccess probleem ... Zorg ervoor dat de. Htaccess in de map / manager directory bevat alleen RewriteEngine off en niets anders ...

[SuperGait]

Ralph, on 18 July 2010 - 01:49 PM, said:

This definitely sounds like a permissions or .htaccess problem... Make sure the .htaccess within the /manager directory only contains RewriteEngine off and nothing else...

Actually it only contains RewriteEngine off and nothing else,after reinstalling etomite I managed to create a couple of snippets and at the fourth snippet, I again got the error:

Forbidden
You don't have permission to access /manager/index.php on this server.

It is very frustrating, could it peraps concern the php setting of the provider?

[Ralph]

Please supply us with additional information so we can better assist you in resolving this issue... The following information, complete with version/release will be of great help... If the issue is browser-specific also include browsers tested and the results of each...

Etomite Version
Server Operating System
Apache Version
PHP Version
MySQL Version

This sounds like a mod_security issue...

[SuperGait]

Ralph, on 02 August 2010 - 12:47 PM, said:

Please supply us with additional information so we can better assist you in resolving this issue... The following information, complete with version/release will be of great help... If the issue is browser-specific also include browsers tested and the results of each...

Etomite Version
Server Operating System
Apache Version
PHP Version
MySQL Version

This sounds like a mod_security issue...

Ralph, thank you for responding so quickly, I wrote down the versions below.

Etomite version: 1.1(prelude)
Server OS: Linux (fedora)
Apache version: 2.2.0
PHP version: 5.2.13
MySQL version: 5.0.90

When You mentionedother browsers, I started testing with different versions
First Internet Explorer 8.0, the problem is still there
Then Googgle Chrome, no problems at all, I'va created 10 snippets with php code, and they all were saved just fine.

The next days I will test some more, but it seems your idea of using different browers does the trick! Thanks a lot!

[SuperGait]

Hmm. the eleventh yime I tried to create a snippet, the trouble started all over again. I don't get why I works for some time by using Chrome, and then after a few times it breaks down again. Not a single snippet or template can be saved after editing or created! This goes beyond frustration, I really hope to figure this out fast.

SuperGait, on 02 August 2010 - 10:02 PM, said:

Ralph, thank you for responding so quickly, I wrote down the versions below.

Etomite version: 1.1(prelude)
Server OS: Linux (fedora)
Apache version: 2.2.0
PHP version: 5.2.13
MySQL version: 5.0.90

When You mentionedother browsers, I started testing with different versions
First Internet Explorer 8.0, the problem is still there
Then Googgle Chrome, no problems at all, I'va created 10 snippets with php code, and they all were saved just fine.

The next days I will test some more, but it seems your idea of using different browers does the trick! Thanks a lot!

[Ralph]

If you would like me to take a hands on look into this issue feel free to PM me Etomite login and server FTP spec's...

[SuperGait]

Ralph, on 03 August 2010 - 09:50 PM, said:

If you would like me to take a hands on look into this issue feel free to PM me Etomite login and server FTP spec's...

Thanks Ralph, but I think I've found the problem. The hosting company has the PHP safe mode on. So I will ask them to
turn it off. I will post a message if when it is switched off

[SuperGait]

SuperGait, on 04 August 2010 - 10:28 AM, said:

Thanks Ralph, but I think I've found the problem. The hosting company has the PHP safe mode on. So I will ask them to
turn it off. I will post a message if when it is switched off

save mode is switched off, but it makes no difference :-(

I've send you a PM with all the data

Edited by SuperGait, 04 August 2010 - 09:25 PM.

[SuperGait]

SuperGait, on 04 August 2010 - 09:25 PM, said:

save mode is switched off, but it makes no difference :-(

I've send you a PM with all the data

Hi Ralph,

Did jou get my mail about the "1" inthe password being a "!" ? I was curious if you found something, to get me going again?

thanks in advance!

[SuperGait]

SuperGait, on 10 August 2010 - 08:26 AM, said:

Hi Ralph,

Did jou get my mail about the "1" inthe password being a "!" ? I was curious if you found something, to get me going again?

thanks in advance!

Sorry Ralph,

The reason the directory was secured is, that it "disappears" after a few days. According to the hositng company some of my fellow webadmin must
be tampering with the files, but now I see that it's gone again. I'm starting to think the hositng companyhas some strange scripting and rights.
If found another domain provider, and I'm going to test Etomite right away!
But thanks for your time, If the same problems occur, I will follow up on this message.

greetings from SuperGait

[Ralph]

Sounds like the right plan of action... Keep us posted...

[vw53a]

Ralph, on 10 August 2010 - 12:43 PM, said:

Sounds like the right plan of action... Keep us posted...

For the record: the concept site now resides at the same host where gerefkerk-coevorden.nl sits, which is in fact one of the two sites that 'll be replaced by the new one. If the other host gives that much trouble I think we'll rename our current one and abandon the other.