Last Updated on Thursday, 12 July 2012 09:44 Written by Carole Bennett Sunday, 15 July 2012 12:00
In Part 1, we covered how to set up your local testing environment with the latest database version from your mojoPortal live site, and how to download and apply the update locally for testing. We’ll pick up from there with the areas that usually require the most attention after running an update, ensuring that your updates are solid, and applying the update to your live site.
The first, and usually the most glaringly obvious issue with upgrades, is the fact that the supporting infrastructure for the UI (“skins”) has a tendency to change frequently, in response to changes from ongoing technology and supporting software, such as Artisteer. Depending on how long it’s been since your last upgrade, the changes may be small, or cause your site to look horribly awry. Have no fear; Joe and his team have been keeping a running update on what changes to apply for each version at “Important Skin Changes” - be sure to go through each step to confirm that you’ve applied all the changes to your mojoPortal skins.Learn More
Last Updated on Thursday, 12 July 2012 09:44 Written by Carole Bennett Thursday, 12 July 2012 12:00
The frequent release cycles of mojoPortal ensure that users have access to the latest improvements implemented by the mojoPortal development team. It’s always a good idea to work with the latest version of your CMS, in order to leverage the best support and features. However, upgrades can also present unexpected issues, and some can be real show-stoppers, especially in the case of customized mojoPortal implementations. Here are some tips on how to upgrade your mojoPortal site without losing downtime due to unexpected incompatibilities.
The first thing to do is to make sure you’ve got the same version of database engine on your local machine as you’ve been leveraging on your hosting server – if your hosting provider is running MSSQL 2008, for instance, make sure you’re running the same version on your local testing environment, right down to the release version – you’ll see more on why that’s important shortly.Learn More
Last Updated on Tuesday, 12 June 2012 02:38 Written by Rodolfo Hernandez Thursday, 14 June 2012 12:00
Elgg 1.8 is out and if you have an Elgg site with version 1.7 we strongly recommend you to upgrade to keep our servers safe.
Last Elgg release (1.8.5) added more security features to keep your Elgg network safe from XSS attacks and also fixed a loophole that allowed users to register without validation which could be used by spammers to spam your site and waste our server resources.
Aside from that, Elgg 1.8 comes with new features which are:
• New group activity widget for user dashboard.
This widget show you a river of new of all your groups the newest, the latest discussions and the popular, the most easy way to administrate yours groups and the groups you own.Learn More
Last Updated on Monday, 30 January 2012 09:47 Written by Rodolfo Hernandez Monday, 30 January 2012 12:00
In this article, I will give you a step by step guide on how to easily run the Upgrade.php script in Elgg 1.8. Sign in to your Elgg site as an Admin and follow these steps:
1. Once logged in, click on the Administration link on the topbar:Learn More
Last Updated on Thursday, 5 January 2012 10:21 Written by Carole Bennett Thursday, 5 January 2012 12:00
One of the great things about working with mojoPortal is the pace at which enhancements and improvements are added to this already-excellent content management system. Joe Audette, the chief architect, is very responsive to enhancement requests, and other members of the community also contribute improvements in features and functionality.
The downside can come when the improvements or enhancements implemented in a particular release include changes in how mojoPortal handles the UI, including alterations in the skins. The included skins are always updated, and periodically, new ones added to demonstrate the increased functionality. However, if you’ve created a custom skin for yourself, or a client, it can create some moments of extreme hair-pulling, and words best not shared with polite company.
To save yourself heartache and aggravation about fixing a custom skin after an upgrade, save this link: Important Skin Changes. At every release that impacts the UI, any changes that need to be made to custom-created skins will be added here. Usually, the two files that you’ll touch are the style.config and the theme.skin files contained in your skin’s folder. Remember that you’ll want to update the skin in the /data/sites/[your site number]/[your skin name folder] to be able to see the changes live.Learn More
- OpenCart Themes on OpenCart – Basics of Launching a Successful Business on the Web
- steam wallet hack on How to Enable Privacy for Comments in Elgg
- steam wallet hack on Customer Can Get a Complete Solution with Arvixe Web Hosting
- Martin on Creating a Multilingual CMSMS Site Using MleCMS Module
- Paul White on Arvixe ASP.NET Web Deployment (How-To Guide)