Problems Editing Templates

[stkeys]

Hi,

 I've tried adding a tracking script to one of my Templates ( purchased from fisinc ) in the "Human view" window of the Template editor ... I got this error

The ../templates/mark_3/index.html file is not writable
Wrote to ../templates/mark_3/b_index.html file
Wrote to ../templates/mark_3/desc.txt file
The ../templates/mark_3/article.html file is not writable

Wrote to ../templates/mark_3/b_article.html file

All templates have been chmod to 777 ( as per instrc. ) so anybody any ideas why the program say's the file is not writable?

[David]

I have the same problem. I can't edit templates for any of my new installs, but can the old ones. I even went as far as chmoding the template subdirectories to 777, and even the files I'm trying to edit to 777. Everything looks right on the install other than that.

I sent a support request to Omar, you should do the same. Give him your cpanel login info.

If I get the answer, I'll post it here.

[stkeys]

Hi David,

Glad to hear it's not just me lol.. although I don't wish you any problems either.

I''ve already sent a couple of Support emails in on some other issues I have, but not had any replies yet.

One of the problems I was having turned out to be caused by my Firewall program ( Zonealarm ) no matter how I set it up certain programs just will not work until I turn ZA off completely.... which is a pain as I've been using the free version for years and only just recently paid for a license... so having to turn it off means I wasted my money. Another program that will not work properly with ZA is Wordpress.

Hope you get a reply soon... and look forward to reading it.

Cheers,

[David]

It may be that this version doesn't have the functionality to manage templates like that. The way the template files are stored (very different from the previous version) indicates this whole part may be handled differently. But I don't see it noted in the documentation.

There is actually a simple workaround for this. Just put your new templates in the templates directory before you ftp them to your server. That way you don't have any need to add or modify templates one you have the site built.

[stkeys]

Just put your new templates in the templates directory before you ftp them to your server. That way you don't have any need to add or modify templates one you have the site built.

by that I presume you mean do all Template editing before FTP'ing and installing them in BS..... I was thinking the same thing today... but then what is the point in having the Template editor feature in BS if we can't use it?

I guess this is a question for Omar or Scott..... hopefully they will pick up on this thread and give us the answer.

[David]

by that I presume you mean do all Template editing before FTP'ing and installing them in BS..... I was thinking the same thing today... but then what is the point in having the Template editor feature in BS if we can't use it?

Yup, that's what I mean. It's the smart thing to do anyway. Then when you ftp your files for a new domain, you won't have to manually edit anything.

I did hear back from Omar. I have a chmoding problem. For some reason, on my vps it shows these chmoded to 777. But they don't seem to really be 777. When Omar used his ftp program to chmod them, it worked. It appears to be a problem with my cPanel. I'll have to have my host help me with it. But I don't need the feature anyway, so I may not take the time.

[stkeys]

I also got a reply from Omar today, here it is.

Blogs use a cache system. If you play with templates, you can temporary
disable cache. Go to ftp, in /common/ folder, and there is a subfolder named
/cache/. Change it's name to smth else, like /cache2/. Then your templates
editing will take efefct immediatly.. you can play with them, when u are
happy, u can go back and rename that folder as it was, /cache/

Hope this helps other members who may have had similar problems.

[stkeys]

Update on my last post......

I tried dissabling the cache then editing the templates again but it still doesn't work.

Looks like I may have the same problem as you David i.e. Server issue.
I'm going to contact them and see what they say.