Following the installation of the NIMVA theme and before development commenced, the LayerSlider WP, Post Types Order, WooCommerce, Contact Form 7, WordPress Importer, MotoPress, and Askimet were installed. The first five of these plugins were required by NIMVA but MotoPress and Askimet were added by DoveSoft.
Subsequently the following plugins were also added.
Although this plugin is installed it is not yet working as Google cannot verify the page due to slowness to respond.
There are three sliders available for this site. The MotoPress slider is good but is embedded in a frame which takes up screen space. View the test page for an example of the MotoPress slider. Similarly, LayerSlide WP is supplied with NIVMA but is too large as seen in the demo. However, it allows for inclusion of text and is ideally suited to full rather than boxed pages. Although it is licensed by NIVMA, the license number is not included and updates to the plugin are not available.
Soliloquy is the preferred option as it is smaller and has its own option in the Dashboard. The lite version is used on the Home page but ensure that when using the Soliloquy Config tab, the Classic slider theme is selected.
Text widget that has extensive conditional options to display content on pages, posts, specific categories etc. It supports regular HTML as well as PHP code.
Microthemer is a feature-rich visual design plugin for customizing the appearance of ANY WordPress Theme or Plugin Content (e.g. posts, pages, contact forms, headers, footers, sidebars) down to the smallest detail (unlike typical theme options). For CSS coders, Microthemer is a proficiency tool that allows them to rapidly restyle a WordPress theme or plugin. For non-coders, Microthemer’s intuitive interface and “Double-click to Edit” feature opens the door to advanced theme and plugin customization.
This site uses the Lite version which only allows changes to 6 objects.
BackUpWordPress will back up your entire site including your database and all your files on a schedule that suits you. Files are stored in the wpcontent/backupwordpress.. folder and can be downloaded for local storage.
#This plugin requires PHP version 5.3.2 or later
- Super simple to use, no setup required.
- Works in low memory, “shared host” environments.
- Manage multiple schedules.
- Option to have each backup file emailed to you.
mysqldumpfor faster backups if they are available.
- Works on Linux & Windows Server.
- Exclude files and folders from your backups.
This plugin generates static html files from your dynamic WordPress blog. After a html file is generated your webserver will serve that file instead of processing the comparatively heavier and more expensive WordPress PHP scripts.
The static html files will be served to the vast majority of your users, but because a user’s details are displayed in the comment form after they leave a comment those requests are handled by the legacy caching engine. Static files are served to:
- Users who are not logged in.
- Users who have not left a comment on your blog.
- Or users who have not viewed a password protected post.
99% of your visitors will be served static html files. Those users who don’t see the static files will still benefit because they will see different cached files that aren’t quite as efficient but still better than uncached. This plugin will help your server cope with a front page appearance on digg.com or other social networking site.
If for some reason “supercaching” doesn’t work on your server then don’t worry. Caching will still be performed, but every request will require loading the PHP engine. In normal circumstances this isn’t bad at all. Visitors to your site will notice no slowdown or difference. Supercache really comes into it’s own if your server is underpowered, or you’re experiencing heavy traffic. Super Cached html files will be served more quickly than PHP generated cached files but in every day use, the difference isn’t noticeable.
The plugin serves cached files in 3 ways (ranked by speed):
- Mod_Rewrite. The fastest method is by using Apache mod_rewrite (or whatever similar module your web server supports) to serve “supercached” static html files. This completely bypasses PHP and is extremely quick. If your server is hit by a deluge of traffic it is more likely to cope as the requests are “lighter”. This does require the Apache mod_rewrite module (which is probably installed if you have custom permalinks) and a modification of your .htaccess file. Visits by anonymous or unknown users will be served this way.
- PHP. Supercached static files can now be served by PHP. The plugin will serve a “supercached” file if it exists and it’s almost as fast as the mod_rewrite method. It’s easier to configure as the .htaccess file doesn’t need to be changed. You still need a custom permalink. You can keep portions of your page dynamic in this caching mode. Your server may not cope as well with a really large amount of traffic. (You’re gaming Digg aren’t you? You’ll need mod_rewrite, the rest of us are ok with PHP!)
- Legacy caching. This is mainly used to cache pages for known users. These are logged in users, visitors who leave comments or those who should be shown custom per-user data. It’s the most flexible caching method but also the slowest. As each page is different it’s often better not to cache pages for these users at all and avoid legacy caching. Legacy caching will also cache visits by unknown users if this caching mode is selected. You can have dynamic parts to your page in this mode too.
If you’re new to caching use PHP caching. It’s easy to set up and very fast. Avoid legacy caching if you can.
Advanced users will probably want to use mod_rewrite caching, but PHP caching is almost as good and recommended for everyone else. Enable the following:
- PHP caching.
- Compress pages.
- Don’t cache pages for known users.
- Cache rebuild.
- CDN support.
- Extra homepage checks.
Garbage collection is the act of cleaning up cache files that are out of date and stale. There’s no correct value for the expiry time but a good starting point is 1800 seconds if you’re not using legacy mode. If you are using that mode start with an expiry time of 600 seconds.
If you are not using legacy mode caching consider deleting the contents of the “Rejected User Agents” text box and allow search engines to create supercache static files.
Likewise, preload as many posts as you can and enable “Preload Mode”. Garbage collection will still occur but it won’t affect the preloaded files. If you don’t care about sidebar widgets updating often set the preload interval to 2880 minutes (2 days) so all your posts aren’t recached very often. When the preload occurs the cache files for the post being refreshed is deleted and then regenerated. Afterwards a garbage collection of all old files is performed to clean out stale cache files. With preloading on cached files will still be deleted when posts are made or edited or comments made.
The cache directory, usually wp-content/cache/ is only for temporary files. Do not ever put important files or symlinks to important files or directories in that directory. They will be deleted if the plugin has write access to them.