Tom, the author of the Mandigo WordPress theme showed me the best way to avoid losing any customisation in the event he releases an upgrade to the theme.
He has built in some automation that makes it so easy – I’m really impressed with this theme!
The following video shows the steps to take – it can be done in minutes, so you have no excuses. Don’t run the risk of losing your customisation. Create your own customised scheme right away.
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=d5e626e9-04c8-4141-aa55-2b98562d7c1a)
Wizzer
Wizzer, your tutorial is most helpful and I created my own scheme but I’m not sure that there is any benefit. It seems there are hardly any files in the scheme directory. Let me explain. First of all, almost everything about my site seems to be filed under:
public_html/wp-content/themes/mandigo
In this directory are things like “page.php” and “style.css.php”
I created a custom page template which I called page-nosidebar.php and I put it in the above mentioned directory. This is the sort of customization that I would hate to lose in the event of a Mandigo upgrade. How does creating a custom scheme help? As far as I can tell creating a custom scheme just copies the files in the following directory:
/public_html/wp-content/themes/mandigo/schemes/blue
But there are hardly any files in that directory! Almost nothing it seems, just a few images! I am a rookie so maybe I am missing something here. Please elaborate on the use of custom schemes and how I can use them to protect things like the special page template I created.
Also I really want to figure out a way to make WordPress blog posts without a date stamp. I suppose a custom CSS styling is needed? IF so, is that the sort of customization that should be stored in a custom scheme?
Hi Bryan, first off – your site looks really good – good content in sidebars too.
OK, Mandigo custome scheme.
When you create your own scheme as you say there are very few files. The main theme is controlled by all of the css files in
/public_html/wp-content/themes/mandigo
The “scheme” you create really only contains items such as your header and any customisation of the page (on WizzerSays I have some blue curved arrows rather than stars as bullets for example)
If I were you I’d copy the /public_html/wp-content/themes/mandigo/schemes/blue folder and rename it bryan (or something relevant) When Mandigo upgrades only files with similar names will be overwritten. Thus the standard blue folder would be overwritten but bryan wouldn’t.
Your page-nosidebar.php should be placed inside your themes/mandigo folder. As page-nosidebar.php is a unique file name it won’t be overwritten if Mandigo upgrades.
Turning to the date stamp – go into the WordPress admin area -
Appearance/Theme Options – about half way down under the section Posts you’ll find Dates – this controls what is displayed on each post.On WizzerSays I don’t use the date stamp either. Just select NONE and the date box you currently have will disappear.
Hope that helps but do let me know if not clear.
hello there from Down under,
wondering if you can help our team widen the Mandigo theme to allow our Amazon products page to work neatly. Of course we need to change header size etc. but Im not sure which and what code to change to widen theme.
thank you
Dan
project bluestar
Dan’s last blog post..Ron Paul Leading Charge to Legalize Hemp Farming
I’ve sent you an email covering this in more detail but…
The problem is the Amazon “boxes” are simply too wide for the available space and therefore overflow into the margin.
The best way to deal with this is to use a template for your shopping page that omits the sidebar. If you watch the video on my post “No Sidebar Template For Mandigo” you’ll see there are other good reasons to do this.
Let me know if you still have problems.
Hey Wizzer, I just found this and tried it, but I get this message: Fatal error: Call to undefined function mandigo_sidebox_conditions() in /MYSITE.com/html/wp-content/themes/mandigo-14/nosidebar.php on line 16. Any thoughts on this? I'd love to be able to use it. Thanks
Hey Matt, like the look you've created at your site.
I'm not sure what this issue is but I see you're using Mandigo version 1.24 and I have version 1.40 now so it's difficult to backtest.
Although I'd recommend updating to the latest version I wouldn't do that until you have a reliable way of keeping your customisation – don't want to run the risk of losing it.
Can you let me know exactly what you've done prior to getting this error message and I'll see what I can do to help
Wizzer