How do I customize Ultimento while keeping my installation 100% upgrade proof
Ultimento 1.5 introduced a very easy way to customize Ultimento as much as you want without having to worry about overwriting your custom changes when a new Ultimento version is released and you want to update your installation. Here’s the step by step:
Configuring the admin
- In your Magento admin, navigate to
System > Configuration > Ultimento Settings - On the upper left corner under the “Current Configuration Scope” drop-down select your Store View (lowest scope level)
- Under the “Ultimento Color Scheme” tab select “Custom”
Customizing the files
Connect to your Magento root directory using any FTP tool and follow the procedure below which is slightly different depending on which of Ultimento’s Magento themes you want to use as a base for your customization:
Customizing Ultimento’s Default Magento theme
If you’re using Ultimento’s original theme as a base for customization:
- Copy the Ultimento template files you want to customize from the “ultimento” folder into the “ultimentocustom” folder (the folders are located under
app/design/frontend/default/). - Copy all the Ultimento skin files from the “ultimento” folder into the “ultimentocustom” folder (the folders are located under
skin/frontend/default/).
Customizing one of Ultimento’s sub-themes
If you want to start with one of Ultimento’s themes, such as Ultimento White for example, it’s the same procedure except that you’d want to copy all the template and skin files in the “ultimentowhite” folders into the “ultimentocustom” folders. To be clear, here’s the procedure:
- Copy all Ultimento template files from the “ultimentowhite” folder (for example) into the “ultimentocustom” folder (the folders are located under
app/design/frontend/default/). - Copy all the Ultimento skin files from the “ultimentowhite” folder (for example) into the “ultimentocustom” folder (the folders are located under
skin/frontend/default/).
That’s it 
.
Noam, should i simply copy over all changes we did for styling as is in to this custom options as far as the fashionpenny project and thats it ? last time you guys did work it wiped all my changes and had to do it all over so kind of important that i have this done fast because we re to go live today… let me know if this should be handled by your team or mine with some easy instructions….
Hi Robert – I am assuming the customization was done on a previous Ultimento version – i.e. before the new “custom” option which was introduced in Ultimento 1.5. Was the customization done directly on the files in the “ultimento” folders or did you create a new folder?
If you created a new folder than all you have to do to update your installation is upload the new Ultimento version.
If you changed the core Ultimento files then you’ll need to simply follow these steps:
1. Using any file comparison software compare your current copy with the original files of the same Ultimento version and carefully note all the differences.
2. Update your Ultimento to the latest release.
3. Re-apply all your custom changes by following your notes from step #1.
That’s it! I hope this helps
.
no , we are on 1.5 , we lost out styling on upgrade and redid it but not the custom option way like we should have.. i just want to make sure Helen can set it up correctly so we don’t foolishly have to restyle again, lol…
you and your team did a great job by the way ,we are laying on final touches and tomorrow is Go time so i wanted to sweep up a bit,..
Noam,
What’s not very clear is how do I for example have the Ultimento New display, and edit that? When I enable custom, the default theme displays.
Should I copy all the files within Ultimento New to the custom directory?
Hi Stefan – sorry if that’s not clear enough in these instructions. I’ll go ahead and update them right now but basically what you want to do in your case is copy all the files from the “ultimentonew” app and skin Magento folders into the “ultimentocustom” folders and work from there.
Thanks!
If all i’ve done is to customize the text in the pages/ccs files and add products to the site…Should I be following the customization procedure or the “no-customization” procedure. I’m confused about what “customization” actually means in the web developer language. (I’m not one, so hard for me)…
Hi Louis,
It’s simple: if you’ve changed (i.e. “edited”, “customized”) any of the files just make sure to not overwrite your changes when uploading the new Ultimento version. So when you upload the new files via FTP, only overwrite the files you know for sure you didn’t touch. On the other hand, whatever you’ve done via the Magento admin won’t get changed or overwritten in anyway when updating your Ultimento.
To avoid having to worry about which files you customized and make sure you will never overwrite any of your custom changes, Ultimento has a special method which is outlined on this very page
.
I hope this clears things up!
Ok..thank you. Waiting on the ultimento 2 download on my newly accessible ultimento login! (thanks for that. Sorry about the non response through that medium)
Hi Noam,
I would like to use a custom ultimento theme. However, I want the name of the design to be a custom name. So if anyone looks at my website code can not see that the website is based on ultimento (sorry).
can I simply edit the app/design/frontend/default/ultimentocustom folder name to a name I prefer?
Hi Tom – yes absolutely! That’s no problem at all as long as you keep the files that are in the “ultimentocustom” folder intact as these are necessary to run Ultimento’s processes.
There are some files in the app – ultimentocustom folder already. Should i go ahead and delete those prior to copying over new files?
Hi Ali – no don’t delete these files. They’re there for a reason
– they’re necessary to run Ultimento.
Hi Noam,
I have 5 websites and would like to customise them all, how would you recommend doing that, should I create 5 directories, ultimentocustom (already exists) ultimentocustom1, ultimentocustom2 etc etc.
Hi Ian – yes that’d be the right way to do it
. Just duplicate and rename the “ultimentocustom” folder and you’ll be all set (this will ensure that the files necessary to run Ultimento will be included for each store).
I also have different websites and have already created the different custom folders in app/… and skin/….
My question is how can I tell magento to use customtemplate-A for website-A instead of customtemplate-B ?
Hi Tom – follow these steps:
1. Login to your Magento admin and navigate to
System > Configuration2. On the upper left corner select your Store View scope (lowest scope level of your site)
3. Click on the “Design” menu on the left and navigate to the “Theme” tab – under “templates”, “layout”, and “skin” put your custom folder name while making sure you keep the “default” field set to “ultimento”.
That’s it
. I hope this helps!
Noam,
Getting some odd behaviour with the compare, wishlist and view buttons in the category view pages (including New Products). In unaltered White (my base theme) there are buttons shown for these features (compare etc.). However, despite following instructions explicitly, the moment I switch to Custom the buttons are lost and the wording “Add to Compare” etc appears. View button is gone completely. This seems to be related to the \ultimento\template\catalog\product\list.phtml file, lines 214-232 which includes a button for Add to Cart but not the others. I thought this file was common to all themes (except New) hence can’t work out how the buttons are delivered and why they are lost in Custom after working in White etc.
Your assistance appreciated.
David
Hi David – make sure to follow the instructions under “Customizing one of Ultimento’s sub-themes” on this post. You need to copy all the template and skin files in the “ultimentowhite” folders into the “ultimentocustom” folders
.
Hello Noam,
allow me to recap the procedure:
Admin >> System >> Configurations >> Ultimento Settings >> Select “Custom” Color scheme
I want to use the Ultimento’s Default theme as base:
Therefore I copy ALL files in /skin/frontend/default/ultimento into /skin/frontend/default/ultimentocustom
Only the files to be edited need to be copied from /app/design/frontend/default/ultimento into /app/design/frontend/default/ultimentocustom.
Is this all?
I edited home-top.html to use the JavaScript slider and placed it into /app/design/frontend/default/ultimentocustom, however the flash slider still appears.
Thanks for your help.
Figured it out.
For anyone who is wondering: The Configuration Scope must be at the lowest level (ie. Store View). I had mistakenly changed the Default Config.
All is well
What if you are only changing files under …./page/cms/ I’m not sure I want to hijack the entire skin directory because I might want some of the new updates that are applied there when they come out. Seems like there should be a better way make sure only the changes made are forked.
Hi Miles – this is the best way with Magento. There is no other way that will work well and keep your installation optimized for speed at the same time.
What about symbolically linking the skin directory back to the main directory if there are no changes to the files inside? That seems to achieve the desired result? Please let me know if I should not do this as the benefits are many and obvious.
Yes you can definitely do that! So under
System > Configuration > Design > Themeput “ultimentocustom” under “Template” only while the other fields should have “ultimento” (if you use Ultimento’s original theme).Also check that the values are correct under your Store View Scope (lowest scope level which you can select on the upper left corner of the admin).
I hope this helps!
Oh so I don’t actually have to create a symbolic link for the skin files. If I understand you correctly the stuff under /app/… is for templates, while things under /skin/… is for Skin, and Layout?
Also just so I understand if I make changes to files under the skin path, is the reason that *all* the files should be copied, instead of just the deltas, for speed?
The reason is because wherever you have your CSS file that’s where it will look for images and other media – i.e. in the same skin folder.
Hope that helps clear things up!
Looking to confirm my basic understanding about the methodology used to upgrade new versions of the Ultimento software on top of prior version of Ultimento. The basic jist I get is that that term version Upgrade is basically a reinstall and owerwrite of all directories except the “UltimentoCustom” directories.
Spelled out in detail this would mean the following….
1.)The Ultimento software upgrades you provide to upgrade existing Ultimento is the same source code that is distributed to new Utimento owners. Meaning Upgrade installations will overwrite all store specific image and look and feel changes that are no implemented as a ultimentocustom themes.
2.)The following Utimento app and skin directories “Utimento, UltimentoWhite, UltimentoBlue, and ultimentonew” were designed to be used by Ultimento as working examples by Ultimento to Demo features and skins included for test drive purposes and a sales tool. Any files that are altered in these directories and subdirectories to setup you stores look and page workings will be overwritten when upgrading future releases.
3.)Ultimeno upgrades do not overwrite any file placed in the “UltmenoCustom” sub-directories located under the app and skin directories and should be the only place used to design your site.
4.) Upgrades that are performed via online instructions are will install new features and look and feel changes in the example theme directories (Ultimeno,UltimentNew,UltimentoBlue…ect). It will be the site owners responsibility examine code changes to the theme directories and determent how best to intergrate those changes to your stores UltimentoCustom directories.
=========================================================
My summary of what resource I think are need to deploy future versions of ultimento in a controlled and professional fashion ontop of your existing magento site.
A minimum of three copies of your production sites should be used when performing upgrades.
Environment usage
1- Dev environment – implement an exact copy of production source and DB. Use this environment to install over your existing Magento store. Switching from the custom theme to the Default theme will be the mechanism used to see the new features and skin working vs how your store look and feel interact with the updates. Areas where behavior is not desirable should result in recodeing your Custom code using the new code provided in the demo directories.
2 Test Env – 1st Copy latest production DB into this env then copy all magento files from dev. Finally, Fully test all store functionality for errors.
3.)Prod Env – Copy all magento files form Test to production. No alteration of prod-data should be needed
Hi John – very nice comment! Thanks for that. It’s all perfect except that I don’t think the “test” environment is necessary
.
My personal recommendation is to run a development installation in parallel with your live store but that’s it.
Thanks for the conformation.
Just some future request stuff off the top of my head that would be a bit more friendly to the customers…I dealt with IBM , MS , Cognos/ many software vendors and really apreciated the some of the stuff they did to reduce risk with requards to upgrades and Lic. Please take these as suggestions and not mr busting chops
1.) Im assuming that you use some type of version control software for Ultimento …if so, almost all produce an automated change summary that would be helpful if provided to users so more informed cost benefit analysis can be done. I kown me as a customer I dont want to spend the the 3-8 hours to install and analysis the Change control logs just to get an idea of how costly (time/Risk) the upgrade will be.
2.) provide installer that looks for previous version / file versions and create a log and backup of the original files for the users. there are a few commercial installers that track this stuff and do it quite well with dependency checking. Event some freeware java based installers work well if money is an issue and it always is
. If possible also incorporate some Methodology/Code changes that could enable an upgrade of code that attempts to reduce the number of manual code changes needed by the customer.
3.) Provide licening agreement that allow users to run their Dev , Test (if they deterine they need this ENV), and Prod. If more then one env is needed to professionally develope and deploy a site, then the Single Licences should account for that. I did see that you are very accomidating when it comes to manualy changing single lic to point to other env which is good, but it does cause the customers some head aches having to request, track and wait for turn around.
Thanks for your input!
Hi Naom,
I’m selling my products only in the EU and don’t need the ‘State’ and ‘Fax’ input boxes. To remove/hide these boxes, should I edit files from your installation (if yes, which) or is it somewhere in the core files.
I tried a extension to solve this problem, but this didn’t work within Ultimento
Beside that, can I set the checkboxes of the newsletter and ‘create an account’ standard off?
Hi Johan – whatever extension you tried to edit these checkout fields should work 100% with Ultimento. I’m assuming that extension has installation instructions for custom themes so that’s what you should be following (or ask the developer about integration on a custom theme).
Since these fields are required by Magento it won’t be enough to edit the template files or hide them. Also you’ll need to do it “the Magento way” without modifying or overwriting any core files.
Can I use OneStepCheckout in combination with Ultimento? I like your way of checkout, but I have to remove some fields, OneStepCheckout (and maybe other extensions) can do that.
Hi Johan – yes 100%. You can use any checkout extension you’d like on top of Ultimento though I’d highly recommend you think about it thoroughly first because nearly all Magento checkout extensions suck
.
OK, I understand what you mean, and at many points I agree
.
As I said I like the way you build it in the Ultimento template, but I have to get rid off some text fields and the check-boxes for the newsletter en ‘create an account’ should be standard unchecked. How can I fix that without changing the core files and your template files (and if I have to, where do I find the files).
Hey Johan – like I said since these fields are required by Magento it won’t be enough to edit the template files or hide them. You need to do it “the Magento way” with an extension (custom or not).
The newsletter check-box can be unchecked by default – just set it up that way under
System > Configuration > Newsletter Optin. Same for the create an account check box – set up your configuration underSystem > Configuration > Optimized CheckoutandSystem > Configuration > Checkout.I hope this helps!
Thanks!
I think I am condemned to usage of OneStepCheckout, I is very important for me that the fields disappear.
New question: my box with the options for configurable product is to width, it is 2 columns width instead of 1 column (the right one). I didn’t change template files, I don’t see differences between the css files of your demo-site and my site. It looks like a div problem to me.
Is this a simple check box problem
, did I something wrong, should I install Ultimento again or do something else? I doesn’t make a difference if I choose the custom template or the blue, white or new template.
Sorry for my many questions…
Hi Johan – you can select from your Magento admin whether the box for the product options takes the whole width or only in the right hand side below the product description. This is a Magento config that can be set globally or on a per-product basis under
.
Design > Display product options inHope this helps!
I’m using the new theme, and for some reason I’m only getting 3 columns of new products on the homepage where your demo shows 4. I opened the home cms, and see it is set to 8 products. I’ve got more than enough products set to new that that shouldn’t be the issue….
Hi Scott,
Please submit a ticket through the account center and we will help you out.
Regards,
Support
Hi I am using the custom theme option and to do this I went into my skin/… folder and copied everything from ultimentoWhite to ultimentoCustom and then I went into my admin pannel and switched the theme I am using to custom and it appears to be working because it is showing the white theme when it was on default previously. Great! But then I went into my app/design/…/default folder and copied home-top.html from the ultimentoWhite cms into my ultimentoCustom cms folder and made the above modifications and nothing happened, it is still using the flash slider. I then also copied over the alternative-top.html over as well and made the changes and I am not seeing any difference. I know this tutorial works because I tried it in the normal directory, but it is not working in my custom folder. Any ideas? Thanks
Hi Tom,
It sounds like you’ve covered most of the basics, but check out our page on using the alternative slider and make sure you read the section on the edits you have to make to home-top.html file. There’s one section where you need to rename one line to point to a different theme if you’re not on default so that could be the issue.
Thanks,
Support
I am so tired of trying to figure this out. I have been working on this for a week. I excatly what you say above and nothing is working. I finally cleared my whole site and started from scratch. So my CMS pages I want to edit, do I need to make that same path within the ultimentocustom folder? Like do I need to put them in a folder with path of design/frontend/default/ultimentocustom/template/page/cms? Because I tried that and it would only pull out some of my changes, for example I got the slider working and changed but when I went into the footer-tabs.html it did nothing, they stayed on the page with the default text. etc etc. What is the easiest way of doing this? Also for my store view can I set all of them to custom or ONLY the lowest level and the others need to be something else? Thanks
Tom
Hi Tom,
Sorry to hear you’ve been having so much trouble. I’m not totally clear on what it is your trying to do or what instructions you were going off of, but there are a few things to know that may help out.
If you’re editing CMS pages then as you said, you’ll want to copy them from whatever theme you’re basing your customization off of and put them in the equivalent ultimentocustom folder. Some of the details of that are in our help topic on customizing Ultimento.
If you’re not seeing all of your changes take effect after doing this its generally one of two things. A cache issue (we recommend you flush everything both in Magento and your browser) or a storeview problem. It’s quite rare, but we’ve come across a few customers that have had to set ultimentocustom only for those storeviews that use that template and keep all the higher levels of websites and stores set to regular Ultimento. The vast majority of customers don’t have to do this, but a few people’s magento installations have this issue. We haven’t been able to tie it to any particular version of Magento or Ultimento and think it may be related to backend system files not updating properly within Magento. A bit annoying, but the setting the configuration as described does the trick.
Try that out and see if it helps!
Thanks,
Support
Hi I have transferred the files to custom from ultimento new, everything worked fine except there are a few changes that I cannot work out how to fix.
The first thing is the new-header-banner has disappeared,
the second thing is the home tab on the top navigation has also disappeared and
the third thing is the layout on the product-grid ‘new products’ has changed.
Can you please advise me how I can correct this.
Cheers
Hi, I have corrected all of the above issues.
Hey John,
Sorry we didn’t get back to you sooner, but great to hear you got it all figured out.
Thanks,
Support
I have quite happily got a ‘custom’ theme working as instructed above. Now I have added a ultimentocustom2 folder for a secondary theme.
How do I get the ‘custom2′ to appear in the “choose your color scheme” section of Ultimento Settings so I can easily switch between the 2?
Hey Darren,
Sounds like you’re well on your way design wise. Generally speaking, the list of templates you see in the Ultimento Color Scheme drop down are hard coded as we didn’t see this as a section that would need regular editing.
You can get around this though if you go to Configuration > Design > Themes. There you’ll see where the theme files are being directed and you can simply change Ultimentocustom to Ultimentocustom2.
Thanks,
Support
‘On the upper left corner under the “Current Configuration Scope” drop-down select your Store View (lowest scope level)’
Sorry if I’m being dim here…what do you mean by ‘lowest scope level’?
Hey Mike,
No problem. Just to give the full overview, if you navigate to System > Configuration and you look in the upper left corner of the screen (Just below the menu that says “Dashboard”, “Sales”, “Catalog”, etc.) you’ll see a box labeled “Current Configuration Scope”. This controls being able to see the websites, stores, and storeviews controlled by Magento. Since stores are subsets of websites and storeviews are subsets of stores, when someone refers to the “lowest cope level” they’re generally talking about storeviews. If you select any of those you should be int he lowest scope.
Thanks,
Support
is the ultimentocustom directory name still valid for ultimento 3.0?
Hi John,
Actually it’s not. This discussion board is only for Ultimento 2.0, you need to go to Commative.com for Ultimento 3.0 topics.
On Ultimento 3 we’ve moved to ultimento-custom as the folder you want to use.
Thanks,
Brandon