jay-august

Any update on this rATRIJS?

Thank you Kristarella, your explanation was exactly what I was looking for. I now have the right taxonomies on the right content types 🙂

Although not a perfect fix, I did manage to get rid of the error by editing more-type-settings.php from line 285 – 296 to this:

$tax = array();
        $stax = array();
        $mytax = $more_types_settings->get_val('taxonomies');
        foreach($wp_taxonomies as $taxonomy) {
            if (!trim($taxonomy->label)) continue;
            $tax[$taxonomy->name] = $taxonomy->label;
            if(is_array($mytax)) {
            if (in_array($taxonomy->name, $mytax)) $stax[] = $taxonomy;
            } else {
                $stax[] = NULL;
            }
        }

This is =not= a perfect fix, but it did got rid of the error. I’m not 100% sure how your custom taxonomies will respond to this!

fps, thanks for the heads up. I will download and install the update once WP has put in their update queue.

THANKS A LOT for fixing my site 🙂 Much appreciated.

//EDIT

Your update is actually downloadable from the plugin page. The button says 0.8.0, the zip file you’re downloading says 0.8.1. After installing the plugin still says 0.8.0, but at least it works again 🙂

You must have knowledge about logical structures in WordPress before attempting such a usually problematic part of maintaining a WP site.

A hosting enviromment is just that, your hosting package, webspace, shared hosting package, your server, your space on the internet.

ofcourse you’re locked out, you’ve just changed the address of your WordPress blog to an URL that probably doesn’t contain your copied-over files…

Copy all your files and folders to your hosting environment. Then open wp-config.php and enter new dbase details.

Now go to your database in PHPMyAdmin or alike, and do a find-replace action in your database tables from OLDLOCALADDRESS to NEWREMOTEADDRESS. After that login to your wp-admin on your NEW address.

UPDATE

this only works when logged in… As soon as you logout, the 404 errors are back.

Having the same problem here. The maintenance mode sucks and should be removed. It only gave me problems since upgrading to 3.0 and since I manage over 35 WordPress sites, I don’t want this to happen all the time!!