Dennis Whiteman

I’m in for the Mentorship program…

I would like to see Thematic considered as the foundation, but with the BuddyPress stuff in the Buddymatic theme included. That would give you a parent theme with all the main features integrated, including BuddyPress, and make creating custom designs very easy because of the all the hooks that can be modified.

In most of my Thematic-based designs, I also usually include a custom home page template in my child themes with six home-page-only widget areas so the client can essentially layout the home page with either stock or custom widgets.

Dennis

When you install MySQL on Leopard and earlier versions, it installs the directory in /usr/local/ as you say, something along the lines of…

/usr/local/mysql-5.0.77-osx10.5-x86

…and then it creates a symbolic link to that directory called mysql. When you upgrade to Snow Leopard, it backs up everything in /usr/local and later restores it back to /usr/local/. However, Apple’s installer does not recreate the mysql symbolic link during the upgrade process. So, there’s no need to rename that directory to mysql, just create a symbolic link to it as the official mysql installer does.

ln -s /usr/local/mysql-5.0.77-osx10.5-x86 /usr/local/mysql

Once you create the symbolic link, MySQL will start automatically. At some point you’ll want to upgrade and this method will leave your previous installations in place.

Dennis

For now I have a work around, but I’d really like to find a longer term solution since we’re replacing manual data entry with this import process.

The work around is to import my XML file on the Mac to a new user and then export the new records for that user to a new WXR file that I then import into the production server. Really, this just means the Linux machines have an issue with the WXR file I’m generating, but I’ll revisit that later when I have more time.

Dennis

Since WordPress uses regular expressions rather than an XML processor on import, that’s one potential source of problems I’ve been pursuing. My Macs running Leopard have PCRE Library Version 7.6 (7.8 is the latest); the two Linux servers where the import only brings in one or two records have PCRE Library Versions 6.6 and 6.7.

All three servers are running Apache 2, PHP 5 and MySQL 5, though there are some minor variations. I should add that I have virtually no control over any server software running on the two Linux servers.

Does it make sense that this difference in the PCRE libraries on two different platforms could be the problem? Anyone have any suggestions working around it?

Dennis

Just as an addendum for anyone trying to solve this problem in the future, there are several existing bugs that have been filed on this issue.

In my case, I’m able to work around it by using post_id instead of postname as the slug.

/content/% post_id%/

This does not affect pages and only affects about 20 or so posts that I’m not going to directly link to anyway.

Dennis

I’m still working on this problem, but it appears that the custom permalink structure I entered is being ignored in favor of providing a year-based permalink structure so…

https://www.site.com/content/1000/

…doesn’t work because I don’t have any posts added in the year 1000. However, I do have posts from 2007 so this displays posts from the year 2007…

https://www.site.com/content/2007/

…not post ID 2007. Obviously a bug of some kind that I working to fix at least on my installations, but I hope this gets resolved in the trunk…

Dennis