Closed (fixed)
Project:
Theme Editor
Version:
4.6.x-1.x-dev
Component:
Documentation
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
29 Jun 2005 at 10:32 UTC
Updated:
16 Nov 2009 at 22:31 UTC
Looking at the code, there seems to be a way to select the newly created custom themes.
This is seemingly supported by theme_editor_engine.engine.
But on how to install it? And where to put it?
Please enlighten me.
Also, is it possible to add it to documentation?
Comments
Comment #1
druvision commentedFor more information, look at the following forum topic:
http://drupal.org/node/20075
Comment #2
druvision commentedGREAT TIP:
If we need to enable users to have immediate previews of a single theme, all we need to do is to make a symbolic link from the "themes" directory to the newly-developed theme. For example, if the name of the new theme is bluemarine_customized, I use the following shell commands:
This will work greatly until there is a theme version which supports installation
Comment #3
aldon@deanspace.org commentedI have to echo the importance of this issue and comment about why the workaround is okay as a brief workaround but is not good in the long run.
First, the administrators of most of the Drupal sites I support don't have access to telnet or ftp so linking or copying files isn't an option for them. On top of that, when you are running off a shared directory, which I do for many of my installs, copying the theme from the theme editor directory which can be specific to each site on the shared directory to the themes directory which is shared by all sites, means that all sites have access to each others themes which can be a real problem.
Comment #4
aldon@deanspace.org commentedWhen you install theme_editor, you need to create a new directory under themes/engines named theme_editor In the themes/engines/theme_editor directory, you need to place the file theme_editor_engine.engine
For more information, see the discussion in the forum entry listed above
It would probably be best to have this information as part of an INSTALL.txt file
Comment #5
druvision commentedThanks, it worked. Leaving it as a documentation issue. Priority changed to normal.
Comment #6
shane birley commented