I've got a substantial update to Redirection just about finished off and ready for release. Rather than dropping this out and running the risk of upsetting a lot of websites, I've decided to try a private beta-test to iron out any final problems.
The new version gives much better management of redirections and error logging, and adds very powerful support for native Apache .htaccess files (i.e. you can use Redirection to edit .htaccess). If this sounds like something you want to help out with then drop me a line. The only requirement for this is that you are familiar with backing up and restoring your site database, or that you have a test WordPress site. The biggest help will be from people who are already using Redirection and have data to import into the new version.
Thanks in advance for any help!
Read more here…
In an effort to remove all invalid links and redirections from my site I've been paying very close attention to my access logs. Courtesy of the list that Redirection maintains I've noticed that my site has been under a prolonged attack.
No, there's no panic just yet, and so far this is not something I'm worried about. The attacks appear to be part of a general 'find any weakness in any website' method, rather than a specific and directed attack.
Read more here…
Redirection 1.7.5 has been released and adds:
HTTP status code 410 added to list of options
Read more here…
Redirection 1.7.3 has been released and adds:
Log delete functions - delete logs directly Update notifications - release notes directly inside the plugin
Read more here…
We generally become WordPress users to create a blog for everyone to see. This can involve the purchasing of a domain name and web hosting. These we treat as black boxes on which the WordPress software is installed, and everything magically works. This is exactly how it should be.
Although WordPress provides a comprehensive management interface, there are times when it would be better to have our own local copy, running on our own machine. There are several reasons we would want to do this:
A working backup of our online site A development site to develop plugins and themes without affecting our online site A testing area to try out hacks and new versions of WordPress without fear of corrupting the live site A staging area to create and verify posts, before releasing them live
Read more here…
In previous guides we have concentrated on the building blocks of creating a WordPress theme. A basic design structure has been defined, followed by enclosing header and footer elements, and finished off with a navigational guide. While important aspects of any blog, they are secondary to its main purpose: the content.
In this fourth and final part we carefully dissect the process of taking the content from WordPress and arranging it on screen. Attention is paid to the many alternative methods of grouping this information, from the many posts of the front page to search results and archives.
We will look at how WordPress distributes the responsibility for this work, and how everything is tied together with the all-seeing all-knowing construct known as ‘The Loop’.
By the end of this guide we will not only have a fully working theme, but we should have enough experience and knowledge of WordPress to be able to extend our theme beyond the basic design presented here.
Read more here…
