Can't Edit Templates

[flyouth]

I had CMSmadesimple version 1.1 installed and was unable to edit templates (I don't know why though, I was able to edit them previously).  So, I upgraded to 1.2.3 hoping that would solve the problem.  It didn't.

What happens is I edit a template, then click either Submit or Apply, and I get a 403 Forbidden error.  Why?

Any help would be appreciated!

[davids355]

I would imagine its possibly something to do with the part in the installation guide where you have to change permissions on certain files/folders on your server using chmod, did you follow the guide completely?

[pixelita]

I am not getting a "forbidden" error but CMSMS says that the file (styleheet/template) name already exists and refuses to edit it. If I change the name in the top box, it accepts it just fine.  I suspect a web host issue, but my query on the forum has gone unanswered.  It just must be some kind of crazy fluke. I hope it gets solved. 

[Metal Beryl]

I am having the same problem now has anyone figured out how to solve this!?

[Pierre M.]

Please all, play by the rules : give more information to help people assist you. CMSms version, hosting context, settings, way to reproduce... and anything unusual in your http logS.

@flyouth : if it worked, you changed nothing and it didn't work anymore, something out of CMSms must have changed. May be hosting context : what does your hosting provider say ? May be you've been hacked : strangness in logS ? May be something else.

@others : yes, the web host may filter things. Again : see your logS and talk with him. This should provide usefull information for the forum.

Pierre M.

[Slagar]

@flyouth: Really sounds like a permission problem Check your chmod and permission settings like david said. Also check your CMS database user has all necessary permissions enabled.

@Pixelita:
Your issue is quite different to the OP, but...

Do you mean that, when editting, you click submit, and it tells you the file already exists?
I think I have had this same problem with UDTs, but for me it is easily fixed. Make sure you have a backup of the stylesheet/template, and try deleting it in the CMS, and remaking it (just paste everything back in again).
Alternatively, when I get this with UDTs, I find if I I go back to the UDT list menu, and click to edit it again, it will be fine.

I'd usually get this when I try to change the name of a UDT while editting it. It seems to get confused, that's all.

I hope that helps anyway. Good luck

[calguy1000]

I've had problems with the 'XXXXX by this name already exists' thing too from time to time

but I can't seem to find a way to consistently reproduce it.

If somebody can find a way to reproduce having two templates or UDT's or GCB's or whatever with the same name, I'll fix it.

[Slagar]

Not sure if this will help you track it down Calguy, but for me with UDTs...

While editting, if I change the UDT name, and hit Apply...
- First press of Apply is successful
- Second press of Apply (or more) causes the "this-tag-already-exists" error.

Changing the name BACK to the original name, seems to work fine for first/second/all cases.

EDIT: I can't seem to get this error at all with templates or stylesheets though... very strange indeed 

[jmcgin51]

I have this problem with Templates in 1.4.1.  I cannot make any edits to any templates; when I try, I get a "Template name already exists" error.

I'm happy to provide admin access (and FTP, if necessary) to one of the Dev Team if they'd like to take a look.

Thanks.

[jmcgin51]

Still having this problem - has a resolution been found yet?  My offer still stands to let one of the dev team take a look...

[Pierre M.]

Hello,

does everything else work except this "Template name already exists" error ?
Please publish you System Info and use the system checksuming tool in the admin panel.
Tell us about your install procedure, your database and your hosting context.
Try config debug on and monitor your http error log.
Any other information that help narrow the problem will save your time and forum readers time.

Pierre M.