Dizkus

Okay, I've had enough time to recover my well-known patience and not resort to foul language... I am doing my first Xanthia theme for a real site... which means that I am depending on XTE for the first time.

Along with every other XTE newbie, I now know never to click on the "Reload Template" link.

I have spent a fair amount of time using the Xanthia admin to modify my theme. Now I'm trying to find a way to save it not only to avoid the dreaded "Reload Template" feature, but to also be able to share the theme with other sites.

Personally, I think that having a "Reload Template" without having a "Save Template" IS A BUG!

If someone has such a thing, please share it with me. This is something I need if I'm going to use XTE. Otherwise, I will have to waste time implementing it myself. And I think that there will be many more XTE themes out there if we make it easy for people to save them and share them.

You cant really just save the theme database info as you need to code the pninit.php file. That way when its added in Xanthia, the proper tables are made with the proper zones/colors/templates, etc. I prefer not to share any of the themes I make because to many people are unoriginal. Its a big complaint about nuke sites is that they look all alike. My personal opinion is that if the site still looks like its a PN site, then the theme needs work. Now, if the site is there to support PN, etc, then thats another thing. I have been working with Xanthia and Encompass (orginal engine behind Xanthia) for about 4 years now. I love it! If you dont want to code the pninit.php, i woudl just recommend saving the SQL of the theme and have someone import it. Thats my lazy way when im just moving a certain theme.

I will add that I have never saved or edited the templates with the database. I use CuteFTP Pro and I prefer to have all the template files open and be able to edit them live with a text editor. That way I can make a quick change, press crtl + S and see my changes. The only thing I go into Xanthia for, is to use the content wrapper, templates admin, and block control. i only use the template admin to add a new template. Which i just type in some random characters for its code. Again, i just edit the hard files, not the DB.

Craig,

Personally I don't bother with the 'store templates in database' option as, IMO, this only complicates matters with no real benefit. I've actually put a case to Larry for the removal of the entire templates in database logic.

-Mark

Oiy. Such a mess.

Mark - You're only right because DB functionality only generates benefits when it is fully implemented, which this is not. (And I'll politely point out that if your only use for a database is as a datastore, there is no difference with storing in the DB or in the filesystem. Some day, the lightbulb will go on and you'll see the light. )

Okay - I understand where this is. Unless someone has finished the module, let's end this thread.