Just curious if you would mind letting me take over future development of this module. I am already working on a D6 version of a theme editor and figured that since this project seems to be unsupported it might be best suited to let someone take over future development.

Comments

arcaneadam’s picture

StatusFileSize
new26.67 KB

So here is my working version of Theme Editor for Drupal 6. It is still in development and I need to work on some cleaning up of the code as I pulled the module files from another module for the file structure. It works and is functional at this point. I will continue to make changes and hopefully can get it made into an official release for this module.

Currently here are the features

  • Edit Any themes files
  • Create and Restore backups of files
  • Add New Files
  • Nice UI using accessible jQuery and CSS coding
  • theme level access control(fully functional with some more advanced features being worked on)

Still to come

  • Deleting files(except for the .info)
  • Access restrictions to php files
  • better control and more revisions of backup

Anyway have fun with it and let me know how it works after it is tried out.

arcaneadam’s picture

StatusFileSize
new31.94 KB

I Messed Up this tar package, use the one below instead

Here is Version 1.1
I cleaned up the module, organized the files and functions and implemented File Deletion and more access control. I will probably leave it at this for now other then bug fixes.

Version 2
I will move forward with a back-up/re-visioning system that is database based and not file-system based.

arcaneadam’s picture

StatusFileSize
new31.95 KB

Here is the correct module package.

nicpottier’s picture

I installed this and I can see the 'Theme Editor' menu option, but I can't seem to actually edit the themes, they all show as 'not editable'. My user has the appropriate permissions and I even made sure the files were world writeable.

Any clues?

arcaneadam’s picture

Well the file system simply checks using the the php function is_writeable() so it might have to do with the directory that it is using to call that file. Is your site setup with any non standard directory structure?

It might also have something to do with the way it is checking the file. If you look at the rendered HTML for the file lists you will see a ref attribute in <li> tag for the file that lists the files path. If the path that it is listing is not relative to the drupal base directory that would be the problem.

walkah’s picture

I am happy to hand over maintainership of theme_editor! pls advise when you've got a CVS account available.

ayaskant’s picture

Is there any security risk involved if I use this on a production site ? When can we expect to have it Drupal certified.

arcaneadam’s picture

There shouldn't be any security risk. You aren't modifying core files or anything only theme files. You do want to be careful about who you give the php editing access to, same as with giving users access to the php filter for content.

I am going to get the D6 version committed this weekend. I have been swamped at work and haven't had a chance to get to it.

arcaneadam’s picture

Version: 4.7.x-1.x-dev » 6.x-1.1
Status: Active » Closed (fixed)

The D6 version is now committed to the repository and on the project page as an official release.

Jeremy Lane’s picture

go into your files and change the permissions so that they are group writable