Posts by aled_hefin

    Using Perch Runway, when I try to login to the admin system, the screen below shows, with a button to "Continue".

    Successfully updated to version 3.1.5.

    When I press "Continue", it simply reloads the same page, "core/update/", and it won't go to the login screen.

    I didn't run any updates, so I presume the customer did it - I take it Perch doesn't automatically update?

    All customer facing pages are now redirecting to the 404 page.

    Any help would be appreciated.


    It won't gp to the next step of the cart process on the staging server, as it's failing the below check:

    if (perch_shop_addresses_set()) {

    Even though the form is submitted, and the post contains similar data:




    [shipping] => test

    [billing] => test

    [submit] => OK!

    [cms-form] => b3JkZXJfYWRkcmVzczpwZXJjaF9zaG9wOlx0ZW1wbGF0ZXNcc2hvcFxjaGVja291dFxvcmRlcl9hZGRyZXNzX2Zvcm0uaHRtbDoxNTY1MzE1MTg1

    [r] =>


    Staging server:



    [shipping] => test-address-1 [billing] => test-address-1 [cms-form] => b3JkZXJfYWRkcmVzczpwZXJjaF9zaG9wOi90ZW1wbGF0ZXMvc2hvcC9jaGVja291dC9vcmRlcl9hZGRyZXNzX2Zvcm0uaHRtbDoxNTY1MzE1NTMw [submit] => OK! [r] => )

    Hopefully a small fix that I can't see!

    I have a form generated with perch_shop_order_address_form(), where the customer selects their delivery and shipping address.

    When the form submits on my localhost, the shipping and billing addresses are selected.

    On the staging server, the addresses aren't set.

    I've updated to the latest version of Runway, checked the versions of PHP , and the POST submitted by the form is the same on both local and staging boxes.

    Do I need to add anything to the page template so that the shipping and billing addresses are set?




    Is there a way where I can create a role, where a user would only be allowed to update certain pages, and that once they update page content, an e-mail is sent to another user with a role of "content adminstrator" or similar? The "content adminsitrator" would then be able to "approve" the change before it goes live.