Modifying a theme - no image, name or description in dashboard
Permalink
Hi,
I'm still new to C5 and sure someone has asked this before but I can't find an answer
I've installed a purchased theme that I want to modify. I've installed the theme in /packages so the directory tree looks like
Then I installed it and set it up from the dashboard and it works fine
Following the guide athttp://www.concrete5.org/documentation/how-tos/designers/modify-a-p... I then copied the entire directory /packages/theme_xxx into /themes and changed the directory name to theme_xxx_new and changed the description.txt file to contain a new name and description so that directory now looks like
When I go to the dashboard the new theme shows but it's annotated with "no name" and "no description" and does not have an image.
What have I missed? Should I just have copied the /packages/theme_xxx/themes directory?
Thanks for any advice.
I'm still new to C5 and sure someone has asked this before but I can't find an answer
I've installed a purchased theme that I want to modify. I've installed the theme in /packages so the directory tree looks like
/packages /theme_xxx /blocks /helpers /themes /xxx /elements /images /js /skins blog_entry.php . . description.txt .
Viewing 15 lines of 16 lines. View entire code block.
Then I installed it and set it up from the dashboard and it works fine
Following the guide athttp://www.concrete5.org/documentation/how-tos/designers/modify-a-p... I then copied the entire directory /packages/theme_xxx into /themes and changed the directory name to theme_xxx_new and changed the description.txt file to contain a new name and description so that directory now looks like
/themes /theme_xxx_new /blocks /helpers /themes /xxx also tried /xxx_new /elements /images /js /skins blog_entry.php . . description.txt .
Viewing 15 lines of 16 lines. View entire code block.
When I go to the dashboard the new theme shows but it's annotated with "no name" and "no description" and does not have an image.
What have I missed? Should I just have copied the /packages/theme_xxx/themes directory?
Thanks for any advice.
Thanks for the quick reply but that's what I have. My directory tree is
Or am I being stupid?
/themes /mynewtheme /blocks /helpers /themes /mynewtheme etc.
Or am I being stupid?
You only need the my theme in the themes folder sorry
Hope that's a bit clearer. If not ill send you a picture.
Sorry abt all that its a pain to type on a phone lol
attached an image
Root/ blocks/ ...contents of blocks folder themes/ theme_name/ Elements/ ...contents Js/ ...contents Default.php Description.txt ect..
Hope that's a bit clearer. If not ill send you a picture.
Sorry abt all that its a pain to type on a phone lol
attached an image
OK, I get the gist, thanks
I've just put the theme folder into themes and that much works. It looks, from your comment, as though I also need to put the blocks and the helpers files into root/blocks and root/helpers as well to have the whole thing work.
Would it not just be easier to rename the package, change the description and put the whole lot into root/packages as though it was a new different package? Then everything is in one place. An update to the original package would not affect my modified package and I could compare and mod files in my package as necessary in the future. In other words if a downloaded theme comes as a complete package then treat mods to it as a new package. Also there would not be any possibility of another extension having a block/helper with the same name and getting a conflict.
I've just put the theme folder into themes and that much works. It looks, from your comment, as though I also need to put the blocks and the helpers files into root/blocks and root/helpers as well to have the whole thing work.
Would it not just be easier to rename the package, change the description and put the whole lot into root/packages as though it was a new different package? Then everything is in one place. An update to the original package would not affect my modified package and I could compare and mod files in my package as necessary in the future. In other words if a downloaded theme comes as a complete package then treat mods to it as a new package. Also there would not be any possibility of another extension having a block/helper with the same name and getting a conflict.
could do that do that 2, try it :)
You don't have to touch the blocks/helpers etc. unless you plan on altering them as well. Recreating a new package from an existing package is not a trivial thing.
Thanks guys.
I think I've got to grips with it now.
I guess what it means is that if you are using a packaged theme and want to change it you copy the just the theme directory inside the package to root/theme and if changing any of the other files copy them to the respective root/*** directory before making changes to the copies.
A slight change to the "doc - how to" athttp://www.concrete5.org/documentation/how-tos/designers/modify-a-p... might help others who made the same mistake as I did.
I think I've got to grips with it now.
I guess what it means is that if you are using a packaged theme and want to change it you copy the just the theme directory inside the package to root/theme and if changing any of the other files copy them to the respective root/*** directory before making changes to the copies.
A slight change to the "doc - how to" athttp://www.concrete5.org/documentation/how-tos/designers/modify-a-p... might help others who made the same mistake as I did.
You've got the concept now.
As I read the How To, this line :
" I'll grab just the simple_blue folder and move it up to (your_site_root)/themes "
needs to say
" I'll grab just the 'simple_blue' folder that resides in the package's theme folder and copy it up to the (your_site_root)/themes folder. "
As I read the How To, this line :
" I'll grab just the simple_blue folder and move it up to (your_site_root)/themes "
needs to say
" I'll grab just the 'simple_blue' folder that resides in the package's theme folder and copy it up to the (your_site_root)/themes folder. "
Yes, That should do it.
Thanks again
Thanks again
I have PM's Matt requesting that change in the documentation.
Themes Yourtheme Elements Default.php Description.txt EtcSorry for the short answer on my phone