See the Finance and Management Business School Website >

The core objectives were to give the customer control over their content whilst also improving the way that the website communicates with their customers.

They can customise the most important calls-to-action across the whole site. This means that their always able to promote their most important services.

Since implementation before christmas, the website has already generated enquiries and converted these leads. With ongoing updates remaining a key part of their strategy, we have no doubt that interest in their services will grow through 2012 as a result of their renewed online presence.

Like what you see? Why not arrange a free consultation with us to see how we can help you to achieve success on the internet. Speak to Andrew on 0121 4690009 or email on andrew@scorchsoft.com.

The Gallery and other modx revlolution plugins (extras) stopped working after moving the Modx Revolution files and database from on server to another. All research into the issue yeilded no results, but after much deeper digging into ModX revolution and the gallery, we have found how the fix this issue. Not being able to add albums to the modx revolution gallery being one of the problems.

What causes ModX revolution modules to stop working after a server move?

Modx Revolution seems to store file path references all over the place. It can make a migration relatively difficult in comparison to other content management system. The challenge is changing all of these references so that that everything starts working again. There are quite a few steps to doing this, so here is what to do:

Fixing ModX Revolution modules after a server move.

Step 1: Correct all database references.

Whether you do it through PhpMyAdmin or via another method, you need to update all of the file references in the database. Once in, open up your modx database. look for the "_workspaces" table and edit the "Default MODX workspace" row to point at the right place.

you will see something like "/home/altoedmq/public_html/core/" or "C:/Program files/Apache ...... htdocs/core/" the important thing to change is the file path before "core/" so that it is correct. Unsure what this value should be? If you have CPanel installed then log in and look on the left hand side for the "home directory" value. Add public_html to the end of this if you are on a linux server for the correct file location.

Next go into the "_system_settings" table. Look through every row. You are trying to identify any of the old references to fix them as with above. Just bare in mind that you will want to preserve the modx references such as "/assets" in the same way that you did with "/core".

Step 2: Correct the config file

Within your ftp client, navigate to "Your Modx directory/core/config/config.inc.php" and edit the file. You will notice within it many references to folder paths relative to the server file system. You will also notice references relative to a domain name. Correct all of these according to the correct server details. This is a similar process to above except you are editing lines of a file rather than database rows.

Step 3: Fix broken Modx Revolution modules.

Some modules have file references within their installed php files. The easiest way to fix them is to uninstall them and reinstall them. You would think that it would be as simple as this, but is isn't. Here are the steps to take in order to actually perform a clean re-install.

1. Fully uninstall the package from within modx
2. Delete the "Your Modx directory/core/cache/" and replace it with an empty folder of the same name.
3. Go into "Your Modx directory/core/packages/" and delete the folder that corresponds to your module. Leave the zip file where it is.
4. Go into "Your Modx directory/core/components/" and delete the folder for the module if it exists.
5. (Optional) delete any _modulename_ tables from within the database using php my admin. I say optional as it may not be essential to do this. It wasn't needed to be done to fix the gallery plugin.
6. Reinstall the module as you would normally.

Modx Revolution fixed after a server move!

And there you have it. Your ModX revolution core should now be working correctly, as should any ModX revolution packages/extras.

We can make web pages for iphone. We can also take your existing website and convert its web pages for iphone. Designing and developing for mobile devices has become increasingly important as mobile smart phone usage rockets. We are seeing a real need for web pages for iphone, android, blackberry etc.

It may not seem like much, but in designing for iphone and other mobile devices we can ensure that the users of your website only need to scroll up and down on the web pages that have been designed for iphone.

Example of web pages for iphone and other mobile devices.

Have a look at the BNI Edgbaston web pages. This website has been designed resize its web pages to fit the screen width of phone and mobile web browsers. Have a look on it's web pages on phone, alternatively try resizing the width of your web browser. You will notice that after a point the web pages resize to fit the screen width perfectly.

Why make web pages for iphone and mobiles?

Making web pages for iphone, android and other mobiles is important. It allows you to improve user experience and maximise the effectiveness of your marketing. It allows you to make the most of your screen space whilst also increasing the ease for which a user can browse through your web pages. There is a good reason why the big hitting websites such as twitter and facebook have designed web pages specifically for iphone and other devices.

Does it take long to convert my websites for iphone?

Relatively no. If you have a 5-10 page website that has been written well then it may only take us half a days work to convert your web pages to have a specific view for mobiles.

What next?

So, you want to convert your site to work on mobiles? Contact Us! Give us a call on 0121 4690009 or drop us an email at info@scorchsoft.com. We will give you some free advice on the best way to move forwards.

Catching and blocking spam emails is, has and probably always will be one of the biggest annoyances on the internet. One fantastic solution to the problem is using a recaptcha field. This method works well... downsides? You have to have a cumbersom recaptcha spam captcha field on all of your forms. This isn't always an issue however it often clashes with design, especially if you are trying to put a quick email form into a small space.

Try implementing a honeypot captcha to catch that pesky spam!

A honeypot captcha is simple. Put a field onto your form that humans won't fill out. Most spam bots search for forms, fill out every field and submit it. If the honeypot captcha field is filled out then you know that it is a spam submission.

Rather than defining the field as:

use an actual text field like this:

The honey-pot pros

• Simple to implement.
• It works against most spam senders.
• It means you can keep control your website aesthetics.

The honey-pot cons

• Easy to bypass if the spammer knows you are using this technique.
• Your website isn't helping to digitize books.
• Accessibility. Someone with a screen reader will see the field and may fill it out. An alt tag has been added to try and prevent this.

I had an issue. When calling an ajax function within a lightbox, if there was a facebook like button being called then it would not render the like button. The facebook like button needs to be rerendered or reloaded using jquery/javascript.

I took this xfbml like code:

and added a class to it like so: 

Notice that I also wrapped the button within another div of class facebook. I then created a function to reload the facebook like button:

This reloadSocial function needs to be called after the ajax load. For example, I wanted it to load once the facebox ajax call had completed using this: