Custom theme documentation outdated?

Answered IV 10 years ago

Hi,


is documentation about creating custom theme outdated with version 3.x?


I am trying to follow instructions on these pages:

https://help.useresponse.com/knowledge-base

Replies (7)

photo
1

Yes, all documentation is only for 2.3.x line. We'll try to update the docs during next months.

if you have specific questions let us know but it's very similar to what we've had

photo
1

Thanks for the info Stas.


I would like to know how to create starting point for a custom theme. I have created a new folder for a custom theme and I can select a custom theme but I would like to know what folders and files I have to copy to custome theme's folder.


Thanks.

photo
1

Igor,

did you review the docs for 2.3.x? As folder structure is the same. In our extra area there is wide theme. You can take folder structure from it

photo
1

Hi,


where can I find extra area?

photo
1

Hi Stas,


Where can we find a full copy of the Default Template, or at least the main CSS? I'd like to customize a template as well, but mostly the CSS, and the guides mention default template locations that don't exist.


I notice the CSS seems to be run through a minimizer or processor - when I change theme.css, what do I need to do to activate that and update the CSS references?

photo
1

Just a bump - any news here on where I can find more accurate documentation, or a default theme to use as a starting point?

photo
1

Sorry for the late reply. All themes are now located in /custom/themes/


The structure of files is described below, but you can use theme.css, theme.js for desktop and mobile interfaces.

  • assets folder (where desktop and mobile folders are located ) In destop folder there should be 3 folders - css, images, js
  • templates (where layout folder is located). In layout you can take standard footer.phtml and header.phtml and put your logic there. We don't recommend overriding other templates

Full documentation about theme customization should be published this month

photo
1

Thanks Stas! If I get time to play around, I'll try that - otherwise I'll look forward to the full docs.


Quick Question - we don't seem to be able to upload the favicon.ico as intended. Nothing happens after we upload and save. Is there a known issue with that?

photo
1

Mike,


You can check if you have /public/branding folder to be writable where favicon is located or replace the icon maually

photo
1

Hi Stas - just wanted to check in to see if the updated docs are done?

photo
1

Hi Mike,


We were so busy with our next release that didn't have time to work on documentation. Will try hard to complete it, but no promised on exact date, so will have to wait.

We always have option to order Theme Customization service so our dev team will handle it.

photo
1

I'm finally able to give this a try, but I wanted to clarify your earlier comments.


You gave the directories of the default theme information - do I need to copy these items, or were you saying that I can use "theme.css" etc to override them? I.E. I can just create theme.css, add whatever overrides I need, and all else will be default?


For Header and Footer, these I should definitely copy into the new theme folder if I want to edit?


I'm going to have to make changes on a live server, so I just wanted to clarify before switching the theme to the new one and tinkering.

photo
1

In general, you need to use empty theme.css in your theme folder and put only classes to override. All the the rest, that you won't touch will be default.


As for header and footer - take default templates, put them into your custom theme folder and change them to match your design.

So all that you've mentioned is correct.

photo
1

Wonderful, thanks for clarifying!

photo
1

You are welcome. Hope it would be easy to customize it for you

photo
1

One final question, sorry - the active CSS on the site is a compiled file. How do I get my changes to compile and be live?


So far, just enabling the theme hasn't resulted in any new CSS being applied.

photo
1

Theme.css should be loaded automatically outside of minified core css. Do you see that theme.css is loaded in firebug or source of the page?

photo
1

Theme.css isn't called on the pages, no. I do see a script that notes the theme selection, so it is enabled, but the CSS file is not loaded.

photo
photo
1

Mike,


Please give me the full path to theme.css from the folder where UR is installed.

photo
1

Web Root > custom/themes/themename/theme.css


Does this need to be somewhere like /custom/themes/themename/desktop/assets/css/theme.css ?

photo
1

Yes, it should be in


  1. custom/themes/themename/desktop/assets/css/theme.css


like in native system

  1. application/3.2.2/assets/desktop/css

If you experience problems with lack of information, the best way to find out is to look into native scheme :)

photo
1

Everything's working so far with the CSS, so thanks again for clarifying.


I have tried to replace the "home.png" on the Home Tab by creating a new version in the same location in the theme (following the native scheme), but this isn't working. Any guesses on why it might not load? This time, the structure/paths are correct. At least the CSS works, so I assume I've got the assets structured correctly.


/custom/themes/themename/assets/desktop/images/home.png


I'm just making it another color, so take your time answering - you've been a big help so far, so no rush.

photo
1

Mike,


When you replace any image, or want to hide it, in your theme.css you should state the new location of that image or override class to not show that image. So in face, new image could be located anywhere, but better save it in assets/desktop/images/ and state this in theme.css

photo
photo
1

I've tried to create a custom theme, by following the instructions in the comments above.

So I created a 'eal-theme' folder (within custom/themes) containing:

\assets

\assets\desktop

\assets\desktop\css

\assets\desktop\image

\assets\desktop\js

\assets\mobile

\template

\template\layout

I've then copied header.phtml & footer.phtml into the \eal-theme\templates\layout folder.

When I then switch the site to use the new theme, the site completely dies, starts sending many errors per seconds and eventually displays a loop error. The errors state:

Fatal error on line 4 in file /var/www/custom/themes/eal-theme/templates/layout/header.phtml, PHP

5.4.45-0+deb7u2 (Linux)

I've obviously done something wrong, please could someone help?

Are their any instructions available yet for creating a custom theme?

photo
1

Stephen,

What version of UseResponse do you use?

photo
1

We are currently using v3.2.2

photo
2

There was a bug in this version. Please update to the latest 3.4 release as it should be fixed with the instructions that you've provided.

photo
Leave a Comment
 
Attach a file