Forum Replies Created

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter booleanvalue

    (@booleanvalue)

    Sorry I havent had the necessary time to set up a new server instance. I have obtained the required sign off from the client in question though. I’ll set up a new lamp stack asap, copy over the data and provide some credentials. Cheers.

    Thread Starter booleanvalue

    (@booleanvalue)

    Cool, I’ll clone up another environment and give you the details for it. Much appreciated.

    Thread Starter booleanvalue

    (@booleanvalue)

    Yep, all URLs and everything look identical. This doesn’t just break permalink on the timeline page, it does it for all links if that wasn’t clear.

    Switching to twenty sixteen theme doesn’t resolve the problem either, its quite a puzzle

    Thread Starter booleanvalue

    (@booleanvalue)

    The Production site has Timeline Express 1.1.8.2

    When I do an update to latest 1.2.8.1 on my staging server, the permalinks break. So, Prod and Staging are different in that respect – sorry if that was confusing.

    The URL’s are all exactly the same. I clone Prod to Staging, everything is fine. Update the plugin, site breaks as described.

    If I update directly on Production it also breaks hence me rolling back to keep the client site live.

    Thread Starter booleanvalue

    (@booleanvalue)

    Yeah, that is the Production website. The breaking changes are on staging/development servers as I obviously cant roll them out to prod and break the entire clients site.
    If you think it would help (somehow viewing a WP generated 404) then I can set up a new public facing temporary server instance.

    Disabled plugin – site works, timeline page shows shortcode.
    Enabled plugin – every page 404’s

    Thread Starter booleanvalue

    (@booleanvalue)

    The site that is working fine and is on the public facing internet is available at http://www.r9accelerator.co.nz/
    This has an older version of WP, the theme and various plugins for obvious reasons 🙂

    Thread Starter booleanvalue

    (@booleanvalue)

    tjerkrintjema – Yeah, I tried the save permalinks trick first. I actually did this on a staging server so its not public facing internet. Given some time I could set up a new instance of everything somewhere if people want to take a look. Its a WP 404 (i.e. nothing in the apache logs etc)

    I’ve deleted and pulled from production and updated the staging server several times over, as well as trying a complete WP install from scratch and just copying over the database and wp-content folders.

    Sorry I got nostalgic with my description and typed something from the past 🙂 I did exactly the same as you, but it didn’t seem to help on Ubuntu 2.4.x
    Thanks for getting back here though.

    I have this exact issue on the same line on my production servers, but not locally. Can you elaborate on the cgi module fix? I’m running php-fpm on production, but not locally in MAMP where the plugin works. Enabling mod_cgi didn’t seem to help.

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