This forum is for churches and ministries using Web-Empowered Church tools or packages. If you are a WEC customer, please submit a ticket. If you are reporting a bug with one of our plugins, please email us. If you are a business entity and want help that you cannot find here, please look at our services.
Notice: we are using new forum software and most messages from last 2 years were transferred. If you had an account before, please login to post a message on the forum.
Skin update
| Author | Message |
|---|---|
|
Written on: 02/04/2011
|
|
|
James Walters
Topic creator
registered since: 09/22/2009
Posts: 6
|
The skin I used as my starting-point has just been updated. Normally I update extensions to the latest version whenever possible, but in this case is it: irrelevant / advisable / good practice / essential / none of the above? How would I do it anyway? Yes, I did it by creating a copy of the updated skin and copying over my adapted css files and tweaking the page.ts to look at the newly adapted skin rte.css ... and I haven't found anything wrong yet ... or any different, come to that. Can anyone straighten out my thinking (if that's what it is ... ) |
|
Written on: 02/09/2011
|
|
 Jeff Segars
registered since: 12/20/2004
Posts: 665
|
James, There's a bit of manual work involved, but its often a good idea to keep an eye on changes in the new versions of your skin. We're typically making minor bugfixes in the TypoScript or CSS and these are fairly likely to affect your custom skin also. When comparing the versions, a diff tool (http://diffchecker.com/ is an example of an online one) can be helpful to spot the differences. If you really want to go deep, the change history for all skins is available at http://svn.webempoweredchurch.org/projects/public-templates/repository/show/trunk. Thanks, Jeff |
|
Written on: 02/09/2011
|
|
|
James Walters
Topic creator
registered since: 09/22/2009
Posts: 6
|
Many thanks, Jeff - very useful Is this a good place to mention that there is a typo (twice) in skin_meadow/skin_typoscript.ts at lines 266 and 267 - "additionalDocHeadCode" is missing the second "i", so maybe the css for IE6 doesn't kick in? James [This article was edited 1 times, at last 09.02.2011 at 11:10.] |
