Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)
  • Broken for me too, if that matters.

    bmkdnf

    (@bmkdnf)

    I think it took me 5 tries to get the upgrade working properly, but you are right doing it in that order works properly – these 4 steps should practically be a sticky here:
    1) Uninstall TML page version completely
    2) Rejiggle the permalink settings to another than back again
    3) Install 6.3.8
    4) Rejiggle the permalink settings to another than back again

    Oh, and another thing – this plugin conflicts a bit with the new version of the ultimate tinycme plugin settings as it takes over the “gear menu” completely.

    TML Pages in 6.3+ are a custom post type (http://codex.ww.wp.xz.cn/Post_Types). Custom post types have been around a bit in the wordpress backend, but the actual support has always been a bit awkward and has come along only somewhat gradually.

    Due to the awkward support a lot of theme developers historically ignored them, thus they tend not to work so well with them (though that is changing).

    Hope that clears some of that up (I’m not a developer of this plugin, just a user).

    You need to sign up for recaptcha here for the keys:
    http://www.google.com/recaptcha/whyrecaptcha

    The “theme” is just one of the color styles recaptcha supports (info also available on the site that link points to)

    For me, it’s just the wordpress.com standard (“Day and name”). Anyway, played around a bit with this. FYI, I’m testing it by opening it from the toolbar (previously called the admin bar).

    1) Changing it to “Post name” worked, and then still worked when it changed it back to “Day and name” or any besides “Default” (?p=#).
    2) “Default” gets the 404 error after the initial update, but after browsing to another page the toolbar link becomes the correct one.

    Basically, after changing permalink settings to anything else then back again appears to “fix” it, but not sure how yet.

    OK, the issue with the blank issue is that for some reason the normal file hierarchy isn’t being called correctly – if page.php doesn’t exist it just sends a blank page when it should fall back to index.php (and so forth).

    I’ve confirmed that the blank page bug happens due to messing with any settings at all – if I install it without touching the settings out of the box it shows the page (I haven’t been able to test anything other than showing the page).

    Even turning everything off again (themed profile etc.) results in blank pages still.

    On mine “Your Profile” is, and both the url when editing the page and the page it redirects to (stub “your-profile”) match, but the 404 error still occurs.

    Problems updating from 6.2.3 (again)
    ?0?) Shows login form even when logged in (intended?!?!??)
    1) enabling themed profiles results in a 404 error when going to the themed profile page
    2) Once themed profiles are enabled (or perhaps changing settings in general, as I did #0 without touching TML settings) all TML pages go blank… again
    3) When it uninstalls, it doesn’t remove the TML pages properly – they redirect back to the main page but are still present (somehow)

    Back to 6.2.3…

    For some reason 6.3.2 just came as an automatic update for me from 6.2.3. I’ve encountered the following problems:

    1) All (non-admin) pages are blank with no html output whatsoever (they give a proper 200 HTTP header)
    2) Thinking removing the plugin and re-installing it would fix that, I tried to remove it, only to get a “wordpress error” stating “Deleting this page will cause Theme My Login to malfunction. If you really want to delete it, please deactivate Theme My Login.”. So, I hacked the admin class (wp_trash_post) to remove the line that errors out so I could remove it
    3) Even after removing the /login/ redirect isn’t removed (and this happens in previous versions as well, in previous versions I generally had to a do a full wordpress wipe and restore to fix; unfortunately I can’t do that online that easily)

    Sidenote: Was able to downgrade back to 6.2.3 successfully

Viewing 10 replies - 1 through 10 (of 10 total)