One important thing when running websites in corporate environments is the secure feeling that updates will work and be compatible. But when your biggest fear becomes reality and websites break down after updating to the latest version here are some step you could follow. You should, ALWAYS, have back-ups, not only because it could crash when updating but also if you experience a HD failure or whatever. If a website is critical for your business and down-time is not done, you can also restore a back-up in a sub dir on the same server with the same settings, and test the update before you apply it on a live website. If you have updated your website and it breaks down you can do the following; If errors occur on the front-end, and you cant fix them within an hour or so, restore a back-up, make a test dir and try again, if it al works well something in the update process went wrong, and you should try again. If it doesn't and you cant get it to work, get help on the forums, and just keep you live website un-updated for the time being. If the errors only occur on the back-end (admin) part of the website, you can take some more time trying to fix it because regular visitors wont notice, and if you cant work it out, the forums will probably help you out. Also make sure that modules you are using are compatible with the new updated version, you can, most of the times, see based on the Php error what file and path is causing what error, if the path is from a module, disable the module and see if everything works well. So what would be nice to see in CMSMS 2.0 for updating problems. If all hell breaks lose and no one else can help you, you can, apart from calling the A-team, make a clean install, export and import your theme, but if you have about 100+ pages and maybe 300 news items, it wont be fast job rebuilding the content. Regular page content and news items is probably the most used CMSMS content, I know lotsa websites have modules and such but they are restored pretty quick most of the times, and if updating really fails you, you have no choice. So it would be nice to see in 2.0 that one can export pages and news items like you can do with themes, this would make complicated updating errors allot less fearful, since in most cases you could be up and running within one hour if you dont have any special modules which are hard to restore content for. I you have more ideas on what people can do when having updating problems, or have an idea on how to make the updating safe/easier in the future and reducing forum topic about updating problems please comment.

Today we will start a new article "Featured Site of the Week" which will show you some of the sites created with CMSMS usually found from "CMS Show Off" forum. This weeks site is brought to us by forum user kovver. I had the pleasure to interview him a bit about the site. tsw) Who are you and where are you going to? kovver) My name is David De Beukelaer and I'm studying in Holland for Waldorf teacher. Currently I live in Belgium and have studied art in Ghent. I work as a freelancer every once in a while, mostly making artwork for myself, but sometimes making sites for friends and relatives. I also do book illustrators and writing but only in dutch. tsw) So what is this site all about? kovver) Its the artist portfolio for me and a friend. I designed the whole concept in photoshop after styling the color palette. We will have regular updates on the site, mostly with links, archive products, etc... Me or my friend will do the updates. I did the design for this version. Another large project of mine is: http://www.anthros.net which is mentioned in eight CSS galleries tsw) Why did you choose CMSMS? kovver) I discovered CMSMS a half year ago. I work with it when applicable and useful. Sometimes i write extras on it or fix bugs, etc. That makes me think that i should mention them more often, end even help on the development. If needed... tsw) How do you create your designs? kovver) Its very useful to make the design completely offline, in photoshop, with guides, color codes and separate layers. tsw) What have been your major problems with CMSMS? kovver) The largest problems are currently the bugs between IE opera safari and mozilla. tsw) But aren't those problems more CSS related than CMSMS? kovver) Mostly it is a horror experience for every designer, included the ones not using CMSMS, but. So to answer the questions above: no problems that can't be solved. tsw) How did the site launch go? kovver) I did not yet get pointers or opinions from others, because the site is only redesigned for three days now. I don't really know how much traffic I receive daily, some 3500 a month I suppose... tsw) In your own opinion what's good about this site and what's bad? What would you do differently? kovver) I’m recently developing an own style in web-designing which leads me to simplicity! I was wondering what makes a site worth looking at and in the meantime proudly presenting a clear overview, with valid XHTML. This is a new episode in my search for it. tsw) Thank you very much on taking the time to answer these questions. Now, what would you like to say to fellow CMSMS'ers. kovver)

• Focus on your CSS skills, they are the basis
• Try, if capable to contribute to the CMSMS development.
• Make your designs in photoshop, know what you want before you change the css.
• Post your designs, take a look and learn form others. Never copy, it might not satisfy!
• I question the overload on css-galleries! So I'm looking for serious volunteers to make one board to connect them all, but how?

Destile webdign to an art. Because kovver says: style life into art. So take a look at http://www.kovver.com/ and form your own opinion. We will try to continue this article series once a week to show you some of the backgrounds of the sites done in CMSMS.

Put the green bar to work for you— whether you're a developer, designer or an editor. I was halfway through development of my first CMS Made Simple site before I really took a look at the Shortcut bar. It sits so neatly out of the way at the right side of the page that I never gave it any thought. Then, one day, weeks into the project, after navigating to the site's primary stylesheet a dozen times — one after another — the power of the Shortcut bar suddenly clicked. Since then, I've put that little green bar to work everywhere, and it's made developing and maintaining sites faster and easier — for me and for my clients. Here are some tips and ideas on how you can do the same, and get more out of CMS Made Simple right now. Activating The Shortcut Menu The Shortcut bar is activated with the Administration Shortcuts checkbox in the My Preferences / User Preferences menu. Javascript must also be enabled in your browser. After that, just click the green bar at the right of the page to access the current shortcuts or to add/modify them. Adding Links Capture any link by right-clicking and selecting "Copy Link Location" or "Copy Shortcut" for pasting into the Shortcut "URL" field.

Development / Design

During development and design, you'll spend a lot of time on the same few templates and stylesheets, and adding new content. Speed access to those functions with these shortcuts:

• Edit Stylesheet / Edit Template Most sites have a few key page templates and CSS stylesheets, and you'll probably find yourself editing them frequently during development. Add one-click access to these frequently-accessed templates and stylesheets for quick direct editing.
• Collapse & List Pages If your site has a lot of pages or complex hierarchy, it can take several seconds for the page list to display completely. Add a shortcut to the "Collapse All Sections" link on the page list, and your page list will display in a snap, ready for navigation.
• Module Help Working with a particular module frequently? Link to its "help" page for fast access to reference on its syntax and features.
• Add Page You'll be adding a lot of pages when you first build your site. Get right to it with a shortcut to the "add new page" option from the page list.

Site Maintenance

Once your site has been developed, the focus shifts to content. You can streamline the process of keeping online information up to date, and reduce the need for user training by focusing editors directly on their content. Give your page owners and editors quick access to the areas they're responsible for with these shortcuts:

• Edit Key Content Your site probably has a few pages or global content blocks that change more often than others. Make a shortcut directly to these key pages and editors won't have to navigate the pages menu to get there.
• Instant News / Events Add a shortcut to "Add Article" and "Add Event" links in the News and Calendar modules to add new items with a single click.
• "Edit My Pages" If your site has multiple page editors, add shortcuts to the pages they can edit for each editor's account. You'll have less to explain and they're less likely to get lost.
• "Change My Password/Email" Give users one-click access to basic account login information by linking directly to the My Preferences/My Account page.
• Site Standards / Documentation Link directly to any site documentation, standards guides or cheatsheets you've developed for your users.

General Tips / Tricks

• Open Shortcut in A New Window/Tab Add '" target="_blank' to the end of the URL in your shortcut to make it appear in a new window. Include the double-quotes, but exclude the opening and closing single-quote, and note the space after the first double-quote and before "target." You can also right-click any shortcut link and select the option to open it in a new window or tab.
• Use Relative Paths For Portability If you want shortcuts to work even if the host changes (such as a development site that will later be migrated to another host), use relative paths instead of absolute paths. You can delete everything through "\admin\" on the left side of the path. For example, to add a page, all that's needed in the URL is "addcontent.php".
• Sort Shortcuts Shortcuts are sorted alphabetically by name (in ASCII order). Add punctuation or numbers as prefixes to display items in your preferred order.

Your Shortcuts

Have you found other handy shortcuts? Share yours in the comments!

CMSMS 2.0 is the largest project I've ever taken on. Not only that, I've basically signed myself up to do this solo. Well, at least the first large bits of work to the undercarriage will be/were done by me. Here is what is done so far:

• ORM
• Migrated javascript (mostly) to jquery
• Versioning on an object level
• Totally restructured API
• Function caching
• Full page caching
• Started installer
• Rewrite of content
• Smarty tags for module api functions
• Smarty tags for admin functions
• Rewrote how admin themes work (smarty templates) and how menus are loaded (xml file)
• Rewrote News to take advantage of module api changes

If I had to guess, I have about 250-300 hours invested in 2.0. It's beyond vaporware at this point... it will happen. Whether or not some features get cut is a different story, but so far so good. Now, to give you an idea of how much work there is to do, here is what is left:

• Finish installer
• Multilanguage
• Versioning interface
• Workflow
• Permissions/ACLs
• Overhaul of language handling -- addition of the language manager to download translations
• Total rewrite of translation center to be database centric and able to create language files for download on the fly
• Admin interface overhaul -- especially content and permissions
• New block types, especially image

These are the major points. There are a lot of little things in there as well... like removing half of the config.php variables, among some other things. I'm guessing that 2.0 will require somewhere in the area of 1500 hours to complete (For those of us keeping score, that's $112,500 at my current consulting rate). It's going to be impossible for me to finish this thing by myself, especially with the timeframes I've made. I estimate the fact that I can devote about 15 hours a week to CMSMS means that will take about 80 more weeks, which puts us into Summer of 2008. I can't let that happen. So, I'm asking for one little thing... HELP!!! I need to start handing over pieces of 2.0 to other developers. I need people with design skills to help mock up what the admin should look like. I need javascript people to help me tie up the interface and make it totally usable. There is a ton of work to be done and many of those pieces are totally independent of the rest of the system. If you're interesting in looking at any of these pieces, please let me know on IRC (it's the best place to have a long conversation). Any takers? Seriously, if there is one thing I've learned in almost 3 years of leading an open source project, it's how to delegate. You can either ask me for a piece to start looking at or toss your skills at me and I'll come up with something... Any and all help is greatly appreciated! Let's this thing out of vapor and into beta! Thanks!

As a designer I love cmsms, its simple, its easy to use for editors, its stable and pretty clean. I found cmsms back when version 0.10 was introduced, now I loved it ever since but there is one thing that keeps bugging me. Cms Made Simple, by default, is pretty small but I for one don't like that the search module is shipped with it, in my opinion not even the news system should be shipped within. The install system (module manager) for modules is so easy that I don't see a reason why modules like news and search would be shipped with it, same goes for allot "user defined tags" off course I mean the ones not used in stock templates. When I build a small website I don't need most of these functions, and if I did I would just import them with the module manager. Most people with speed issues delete all unnecessary modules and functions to increase speed. Why not have it that way by default, its only a matter of seconds to import a module if you need one. This way cmsms would keep getting known as a simple system and easy to expand if needed. So for CMSMS 2.0 I would make the following changes to the module managing system. Make some changes to the module manager and get 3 tabs like.

• One list of top 10 most used modules. Which could be news, search, FEU, FCKeditor, etc.
• Functions list, all tested and stable functions ready to be imported for user defined tags.
• All other modules the same way it is now.

This way there will be less unused files on your hosting account en get the most speed out of the system as possible. Drop a comment if you think different about this. regards, Signex / Benjamin

In Part 1 I wrote about choosing a hosting package (shared/VPS/Dedicated) this part I`m writing about how to choose a webhosting company. In my country(Holland) hosting prices vary allot, I've seen a couple USA hosts and it isn't much different, only difference is that bandwidth is way cheaper in the US then it is in the Netherlands. One of the problems with choosing the right company is that you cant always see who is behind the beautiful corporate looking website, because it just could be a 16 y/o just trying to make a quick buck, not caring about his costumers at all. Which makes it even harder is that prices vary so much, and off course nobody wants to spent too much on something that you can get way cheaper. The first thing for you to decide is how important is your website for you, or how much is your client willing to spent. You can get a shared hosting package for 10$ a year, but the same package costs 100$ a year somewhere else, so where is the difference? here's a small list of things that could make this difference.

• Do they make backups on a second server
• Do they use an A brand for their hardware
• Are their spare parts on the spot in case off hardware failure
• Which datacentre are they located in, try to find reviews or opinions
• What Control panel do they use, Directadmin is cheaper then Cpanel
• Do they have phone support, or only mail support
• Do they have a 24/7 phone support when your server is down
• What is their write-off period for a server, 3 or 5 years can make a big difference

Probably the thing that impacts price the most is whether they oversell or not, and how much. I read studies from dutch webhosters that only 20 to 30 % from the sold traffic and hard disk capacity is used by their costumers. So basically they can sell 3 times what they can handle. This sometimes means that on a single shared server there are over 500 costumers, so when its a little busy on your server, serverloads get high and your website will be slow, this often resolves in new topics being created complaining CMSMS is so darn slow, which in most of the times just isn't the case. So ask your host how much costumers share a server, or how many VPS`es are created on your server. Most good webhosters will proudly tell that they only put about 100 costumers on a shared server (depending on their server hardware). But don't be surprised that their prices are 5 times as much as some other webhosting companies. So finding a good hosting company depends on your needs and budget, but whatever you choose always ask for a "try before buy" package for about 48 hours and make a CMSMS installation and see how it does in daytime and nighttime. Beware that some hosters will putt these packages on empty test servers, so be sure your "try before buy" package is on the same server as when you buy your package. Here are some other things you could use to check out a company.

• Find reviews from other costumers
• Ask about the hardware they work with
• Ask how long they exist
• Try out mail and/or phone support, is it fast enough for you
• Guaranteed uptime? then what is the compensation when they fail
• Prices to good to be true? ....they are
• Ask uptime reports from the last 6 to 12 months

I hope this will be to good use, suggestions and comments welcome! Signex / Benjamin

I know this topic isn't really about CMS Made Simple, but I see quite allot topics in the forums with problems that would never occur if everyone had the right web hosting company for their CMS Made Simple website. Basically this post is split in 2 entries; Part 1: Finding out the right solution for your website which suits your needs. Part 2: Finding a suitable company, comparing price vs. options, testing the chosen company. Step 1: Decide what kind of website it will be, and what kind of hosting it will need. basically this can be divided in 3 options.

1. A small personal website - Shared hosting will most likely fit your needs.
2. A corporate website (small or medium sized) - Most company websites need to be more stable a need en more secure hosting platform, but sometimes a whole dedicated server just isn't worth it. Go for a VPS (Virtual private Server).
3. A big community/corporate website - Go for a Dedicated machine just for you.

I'll try and sum up the pro's and con's about these 3 options. 1. Shared web hosting.

• Its very cheap.
• Less secure, if other people use broken scripts and a hacker gets in, most of the time the whole server gets defaced.
• Less stable your websites speed can be heavily affected by other users.
• Not really flexible in most cases.

2. VPS Hosting.

• Cheaper then a Dedicated machine, more expensive then shared hosting.
• Way more stable then Shared web hosting, you'll get guaranteed RAM(on Linux vps'es you'll also get burstable RAM) and CPU. Therefore you are not affected by other vps users on the same server.
• More Secure, if another VPS on the same server crashes because of software errors or gets hacked, you`re not affected.
• More flexibility, you can choose your own Operating System, your own Control Panel, and basically all software you need.
• You can do remote Reboots, you can get SSH access (possible on shared hosting too, but not many web hosters will let you gain access).

3. Dedicated Server.

• Pretty expensive, you cant divide Control panel licences to multiple users also.
• Most secure option .
• Most stable option.
• You can be in total control.

Remember when choosing for option 2 or 3, packages are managed or unmanaged. It's also different per web hoster what they see as managed and what not. Some web hosters say its managed when they only install the OS and Control Panel for you, and others will also keep everything updated, fix problem etc. etc. So make sure what you want is what you get. I would advise you to let the web hoster make of contract of what will be managed by them so no mistakes can be made, and you both have an agreement on paper. When you have decided which hosting package is the right one there are a couple other choices you have to make. Step 2, is choosing your OS. Which OS do you prefer. I personally Like a Linux OS for servers. But CMSMS will run on both Linux and windows. If you don't care what OS your package has, go with the one your web hoster has most experience with, this can handy when kernel panic arises. Remember though that Windows hosting is more expensive because of the licences needed. Step 3, will be choosing a Control Panel. CMSMS runs on all Control Panels, so this is a choice you can make on what you prefer, I personally like Cpanel because is has allot of functions and options, and its very stable. A downside about CPanel is that its WAY more expensive the most other Control Panels. Here are some well known Control panels.

• Direct Admin ( easy of use, but not many function, its cheap though)
• Plesk ( not much experience with it but don't like the interface, more expensive then Direct Admin)
• Cpanel (Lots a functions but its really expensive)
• VHCS (Open source, when I found CPanel, this wasn't a stable control panel then, but have no recent experience)
• Helm / windows only ( No experience with that one at all)

So that choice basically comes down on budget and personal preferences. Step 4, Configuration options and other software needed. This is a just a list of things that you'll need to run a cms website smoothly.

• Apache when using Linux, or IIS when using Windows
• PHP 5.x (php 4 will run with the current cmsms but cmsms 2.0 will require php 5)
• MySQL Databases (only 1 Database is required for cmsms, but make sure you get at least 3 to 5, for testing other software, or beta's.)
• PHP safe mode OFF (This isn't required but Safe Mode ON in php, I think, really is annoying, and doesn't work well with CMSMS)
• PHP Memory Limit set to at least 16MB (default is 8MB, and this works well for simple CMSMS websites, but bigger ones with lots off modules will need at least 16MB)
• PHP Max Upload set at 10M (default is 2M, find a host which is willing to set this at 10M, again this isn't required though)
• GD or Imagemagick (not really required but very handy)

Those are basically the things you need for running a CMS Made Simple website smoothly and stable. Any other functions and options you can decide by yourself, things as off-site Back-ups, monitoring etc etc. Do remember though that there are so many ways to configure a server that its always important to ask for a test account for like 24 hours, before signing a contract or placing a order. You can use that time to make a install and playing around with it, install and un-install modules test if your site still runs smooth when 7 modules are called upon the same page. Part 2 will be done in the next 2 days, I hope. If I forget sometimes, or made a mistake, please comment. Regards. Signex / Benjamin

Just a quick bugfix release. The reason is was pushed out quickly was because of issues installing on Windows machines, and had to be handled immediately. It also fixes two different problems with breadcrumbs that people were reporting. We've thrown in a couple of extra bugfixes as well. The ChangeLog looks like:

 Version 1.0.4 "Lanai" -- Jan 23 2007 ----------------- - Fixed issue with number of queries not showing up properly at the end of index.php - Fixed issues with breadcrumbs, including nodes not showing up and duplicate nodes showing - Fixed the warning that showed up in the 25 to 26 upgrade script if you didn't have any events - Fixed bug with installer where it doesn't write windows paths correctly - Fixed issue with Search where it would mess with the letter case when showing the highlighted text 

Thanks!

Hey Guys n Gals, If you're running a good install of 1.0.2 here's the way I go about upgrading to 1.0.3. Works fine, and has been tested on both an IIS and an Apache install in the last couple of days. This update is recommended as some security issues have been fixed, and the contact form now uses Captcha which can of course limit spamming of your site. Download the upgrade zip or tar. Make sure that you are LOGGED OUT from your site admin! Extract the files in the archive somewhere safe and remember where it is! FTP, SSH or copy the files into the root directory of your site. If you now log into your admin with your usual username and password there will be an option in the main part of the admin interface to upgrade, so click away and you should be up and running in no time! Take care all, and enjoy 1.0.3 Ade (3dcandy)

Ok, so I keep spouting off about the goals of CMSMS 2.0. At this point, there are like 40 goals and all are equally important. You've heard it all before... Oh well, I'm bringing up #41 #41: Serious, concise, functional and documented API. What does this mean? CMSMS 1.x has an API of sorts. The module creation parts of the API are probably the most organized of the bunch. Most other parts of the CMSMS code are scattered through out smarty plugins, global functions, poorly named classes that should be called staticly, etc. One of the things I took on early in the 2.0 development cycle was the formulation of a consistent API to work from. And honestly, the lib/classes directory was on the right track. It just wasn't implemented as well as it could. Live and learn... 1.0.x has too many global functions for doing random things. I wanted to cut all this out. Also, there are too many $gCms->GetSomethingOperations() methods. This is stuff that can all be moved to static methods in classes. index.php and include.php were both WAY too messy. I wanted to offload a lot of that stuff into clearly marked methods, using as much DRY (don't repeat yourself) development as I could. And, I wanted to "namespace" all of the CMSMS classes so that they don't get in the way of other classes that might be used for modules, addons, etc to the system. Since PHP doesn't use real namespacing, every class starts with Cms (CmsTemplate, CmsApplication, etc). Because of this consolidation, I could take advantage of the autoloading feature in php5. So I get two benefits with this... no require(_once) statements littering the code, and no files loaded into memory that aren't needed. So, at this point, 90% of the CMSMS code has been converted to this API setup. index.php and include.php are readable, and memory usage is way down. In fact, I've segmented it in such a way that it could almost be used as an API for other php applications. As an example, the new installer is a totally separate application. It doesn't use anything really CMSMS specific, instead it just includes the bare minimum and pulls out what methods it needs for the database, smarty, etc. I've also documented the code as I'm going. There is still a lot more to go, but it's coming along. We'll be dumping doxygen docs nightly so that people will have quick access to the classes and methods. I've already been dumping docs of the svn builds out, though it's not guaranteed to not change drasticly before 2.0 is released. http://cmsmadesimple.org/api Maybe someday we can break out the API and have a framework for other apps to use. That would be pretty slick. Ted

Yesterday I made an entry about CMSMS getting bigger and having a fair amount of users. Now, there is also a downside to this. Getting more attention will also attract hackers, knowing when they can get into one CMSMS website they can get into a lot more. However, the development of the core is done by a of couple great developers. I don't think the CMS Made Simple core would get into a lot of problems when getting bigger and having more users. Also, they would be releasing patches quickly when serious security holes would occur. But how about the modules? And I'm not talking about the much used modules as they will grow and get updated with the core system because so many people use them. But the more unknown modules which don't get updated very often. Those modules will probably cause potential security risks in the future, since scripting never stands still and new vulnerabilities get discovered every now and then. Now we all know that using GPL/Open source software comes without warranties, and using it is at your own risk, but when old modules get security issues CMSMS gets blamed, or at least associated with the vulnerability. This is kinda the way Joomla got his bad name in my opinion. Joomla as a clean install combined with decent chmodding is pretty safe, but with so many 3rd party modules its hard to keep track of what's safe to use and what's not, maybe not for the hardcore coders between us but it is for many others. So what would be a good way to "protect users" against the risk of using older not updated modules? Maybe a new module category in the forge called "Not updated in the last 12 months - could have potential security risks and/or isn't compatible with new core systems" and automatically put all the modules in there which have not been updated in the last 12 months. I'm really interested in how other people think about the module security. Am I just paranoid or could these thoughts be potential ideas? Drop your thoughts in the comments! Regards Signex / Benjamin

Yes, it's incredibly overdue, but it's finally released. This is basically just a bugfix and security release. It's released in both the full download version, and also a diff installation that you can overwrite an existing 1.0.2 installation with only changed files. The security issues were not major by any means, but it's still good to patch XSS issues. The ones we had were non-permanent and didn't cause any damage to your site, but they still needed addressing. The changelog goes as follows...

 Version 1.0.3 "Kauai" -- Jan 18 2007 ----------------- - Fixed several non-permenant XSS vulnerabilities - Fixed issue with breadcrumbs plugin displaying root node multiple times - Fixed issue with multiple events being entered - Removed global references to $db from the admin and include.php - Added a "Modify Events" permission - Added event for "Change Group Permissions" - Added ability to select a file for the Link content type - Added ability to specify default boilerplate page content - Fixed print plugin output so that it's xhtml compliant - Added text direction to languages for suppot of languages like Hebrew and Arabic - Fixed issue where 2 installs on the same domain shared login sessions - Fixed issue with contact form with pretty_urls turned on - Fixed issue with LoadStylesheets() not loading the modified date - Changed search schema layout. Now allows for expiration dates on entries - Changed the icon for global content so that it doesn't look like the Gentoo logo - Fixed issue with expanding content in the content list when user didn't have the Add Page perission - Added catpcha module support to the contact_form plugin (you still need to manually install the Captcha module for this to work) - Added messages when admin log is cleared - Much much more 

Enjoy!

Browsing thru the development part of the CMS Made Simple website yesterday I noticed that there are almost 100.000 downloads of the CMS Made Simple Core. With the release of 1.0.3 It cant take long before it reaches this magical number. With the plans of CMSMS 2.0 coming with all the nice new features it can only get better. Off course it will take a long time before stable 2.0 series will be released but I cant wait for the first beta's to be released. So I would like to take this first blog entry for me as an opportunity to congratulate all the people that supported CMS Made Simple, whether that is with development, time in the forums, donating or just by using it. More serious entries will follow soon! Regards, Signex / Benjamin

Hi all, It has come to my attention that one of the biggest topics on the forum regarding CMSMS is a speed issue. Although 2.0 will have a page caching feature, 1.0.2 can suffer sometimes from slow page loads. To combat this, you should try uninstalling and deleting all unnecessary modules that you have in your setup. This can quite often lead to a nice speedup! Don't forget that custom tags that are installed can slowdown page loads and also unused translations... In the meantime, there is also a tag available which replaces the current content tag with ccontent. This caches the content and has resulted in a nice speedup on the sites I have tested it on. Thanks to cyberman for this! To download the cache tags, please goto http://dev.cmsmadesimple.org/projects/cache/ Bear in mind that you will have to alter the template and/or stylesheet that your site uses to make the cache tags work! Right then, till the release of 2.0, bear these points in mind to keep your site nice and responsive... Regards Ade (3dcandy)