After updating XOOPS to 2.0.17 a few months back, I ran into a problem with certain users not able to see group specific blocks after updating. The users would authenticate, but then not see any content that was “member only”. I was hopeful this would have been resolved with 2.0.18 but it still remains an issue. The problem:

The solution:
In your XOOPS directory: /kernel/session.php

change:
var $enableRegenerateId = true;
to:
var $enableRegenerateId = false;

(Original fix documentation for 2.0.17: http://www.xoops.org/modules/newbb/viewtopic.php?topic_id=62411&forum=2&post_id=281576

url: http://www.thetradecoach.net

SDAC Inc. provided:

• XHTML/CSS programming
• WordPress theme customization
• WordPress CMS setup and configuration
• Custom PHP Programming
• aMember/PayPal Integration

technologies used:

XHTML, CSS, WordPress, PHP, aMember

front end:

The client approached me with a WordPress theme already picked out and in place for a basic blog. He wanted us to customize it for a content management system (CMS) which included multiple levels of membership and had public and private pages and post.

back end:

This CMS was created using aMember, a few WordPress plugins, and some custom template code to keep part of the site private for paying members only. When a member logs in they will see content appropriate to their user level per the membership package they paid with. This is the first site we worked with that used multiple levels of members - and displaying content based on the user level. Amember is used to automatically create WordPress members after their payment goes through and will expire the members when their membership is up.

lessons learned/random thoughts:

It would be great if we had more control on groups (user levels) could see. We also ran into some WordPress bugs with displaying private posts in some of the default WordPress functions and hope these will be fixed in the next version.

If you use Google Analytics on your web site, you should update your tracker code that is placed in your code. The new tracker is faster, and offers added tracking functionality (See Google's announcement)

New Code: (put your tracker ID in where you see the X's)

While you are updating your code, you might also want to consider moving this and any other javascript to the bottom of your web site for improved performance.

url: http://www.muniwireless.com

SDAC Inc. provided:

• XHTML/CSS programming
• WordPress theme
• WordPress CMS setup and configuration
• Custom PHP Programming
• Migration from ezPublish to WordPress
• mod_rewrite Programming
• Server Migration

technologies used:

XHTML, CSS, WordPress, PHP

front end:

The client approached me with a design in progress. From that, I created a basic WordPress theme and then further revised it after more design decisions were given to me.

back end:

This CMS was created after the client decided they wanted to migrate from ezPublish to WordPress. We exported all the data, mapped it to the WordPress tables, cleaned up the code, and imported into WordPress. We then created custom rewrite rules to make sure all old URLs would be directed to the new WordPress URL structure. This is a complicated WordPress theme with lots of conditional logic and some custom PHP programming for Openads integration.

lessons learned/random thoughts:

Overall, this rivals only one or two other sites in terms of sophisticated template logic and I learned a lot in the process of creating it. We also learned a lot about WordPress that we never knew before when importing and mapping the data from ezPublish into WordPress.

If you would like to exclude one post from your blog, archive, search results or wherever you need to on your blog, you can do so by putting in a small piece of code within the particular WordPress loop:

The following example will show all posts except for the post with the ID of 179:

This is something that I get a lot of requests for and is very useful in a number of situations.