Active
Project:
Theme Editor
Version:
7.x-2.x-dev
Component:
User interface
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 Aug 2011 at 16:28 UTC
Updated:
18 Jul 2012 at 22:46 UTC
When I try to use a theme, I get the following message:
Theme Editor's is missing some requirements! Please visit the status report page for more info.
In the status report, there is some error message for the theme editor about this private file system. Although, my configuration is OK, since Drupal wrote its .htaccess if the folder. I lost a lot of time looking here what was wrong.
In facts, as explained in the README.txt, I forgot to set the sites/example.com/theme_editor in the settings of theme_editor.
May be the error message on the report page is misleading?
Tx for your job anyway!
Comments
Comment #1
arcaneadam commentedIt is misleading. It'll be changed before a stable version is released. Thanks!
Comment #2
msDrupal commentedWhen Theme Editor installed, I am getting Private File Directory not set. Please vist the file system configuration page to correct. error message. I am on Windows 2008 R2, SQL Server 2008 R2, IIS 7.5 platform. I created "private" folder as in inetpub/wwwroot/sites/default/files/private and specified the path as sites/default/files/private, but still getting the same error. I'd really appreciate it if any one could help to resolve this issue.
Comment #3
msDrupal commentedHey, it is fixed :)
My colleague resolved this by creating a directory at C:\inetpub\wwwroot\theme_editor (changing the name from private to theme_editor for debugging purposes - directory name doesn't really matter.)
Then added that path (such as C:\inetpub\wwwroot\theme_editor in our case) in Appearance --> Settings (tab) --> Theme Editor Settings (menue option on top-right corner) --> Directory for edited themes (field on top of the page). Note: this directory must have write permission for Drupal.
Walla and good luck
Comment #4
gandhiano commentedI get the same problem and it's basically rendering the module useless, because it refuses to act in any way.
Comment #5
gandhiano commentedOk, now I understood the meaning of being misleading - the message itself is misleading, because it points to the wrong place of configuration. One has to edit theme editor settings, not drupal file system settings.
Comment #6
Taxoman commentedSee: #1172232: Theme Editor not working at all (unless you follow THESE steps)
Comment #6.0
Taxoman commentedSimple edit