Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter terrainnova

    (@terrainnova)

    Was just using the clone button at the bottom. Instead I needed to create a new menu. Solved it myself. Thanks though – really appreciate it.

    Hello,

    we deactivated all 24 plugins one by one and couldn’t get Yoast to work – we see the same behaviour as in the snapshots by OP. We run WP Version 4.6.1 and the latest Yoast version (= 3.5 at the time of writing).

    Is someone from Yoast looking into this?

    We’re starting to evaluate our options for moving from Yoast for this site. Any idea how not to lose all the meta work done on the (dozens of) posts?

    Thread Starter terrainnova

    (@terrainnova)

    I’ve looked at your link and I think I’ve done the equivalent things to what’s there.

    I’ve also deactivating all the plugins (moving plugins to plugins.hold).

    I narrowed it down to the w3tc plugin preventing me to login. I’ll deactivate it (or just the login protection) and I’ll probably be ok.

    Thanks for your reply.

    Hello,

    since you guys are talking about essentially the same thing I’d like to submit a question for, let me chip in with a suggestion / possible solution. Would you see the following as a viable approach(or are there any problems I haven’t foreseen)?

    1. You setup a single github repository for your site. One repository, one master branch.
    2. You setup Revisr in your production WP version and connect it with the github repository.
    3. You use WP Staging to create a staging WP version – by definition it is also connected to the same github repository
    4. You do some work on the staging version and push it to the github repo.
    5. You test the changes in the staging version and make any necessary further changes, which you again push to the github repo.
    6. Once happy with the result existing in the staging, you switch to the production version and pull the changes from the github repo.
    7. If you find any breaking change or any change you want to revert back from, you identify the working version in the commit history and revert to it in the staging version. Then you push this revert to the github repo and pull the change in the production version – the process is similar as in the case of adding a new feature.

    What do you think of this? Are there scenarios I’m missing? Would it work at least for simple scenarios of small teams managing a WP site not needing to make changes simultaneously?

    Thanks for your feedback, hopefully it’s an idea for a solution for you too. At least until WP-staging provides push to production features:)

    Thread Starter terrainnova

    (@terrainnova)

    oddly this is back to working now without me doing anything to fix it. The only suspicion I have of what could have been the cause is of some 500 errors seen in the logs in the admin side.

    Thread Starter terrainnova

    (@terrainnova)

    I am able to view previous commits.
    I see no obvious errors.
    When I visit domain/wp-admin/admin.php?page=revisr_new_commit to do a new commit I see no files under Stage Changes even though the number of files has changed in the top admin bar (it went from 171 to 172 untracked files when I deactivated a plugin).
    Doing a test commit (right after that deactivation) I do get the following error message

    # On branch master
    # Changes not staged for commit:
    # (use "git add/rm ..." to update what will be committed)
    # (use "git checkout -- ..." to discard changes in working directory)
    #
    # modified: myrepono/data/CACHE-INDEX-DCEA6DCAE93CD1B107E5CAC67F47AA47.dat
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/css/qppr_admin_style.css
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/filters-hooks-helper_funcitons.txt
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/fonts/qpprfonts.eot
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/fonts/qpprfonts.svg
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/fonts/qpprfonts.ttf
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/fonts/qpprfonts.woff
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/js/qppr_admin_script.js
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/js/qppr_admin_script.min.js
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/js/qppr_frontend_script.js
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/js/qppr_frontend_script.min.js
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/js/qppr_meta_redirect.js
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/js/qppr_meta_redirect.min.js
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/js/qppr_pointers.js
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/js/qppr_pointers.min.js
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/lang/quick-pagepost-redirect-plugin-en_US.mo
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/lang/quick-pagepost-redirect-plugin-en_US.po
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/lang/quick-pagepost-redirect-plugin-es_ES.mo
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/lang/quick-pagepost-redirect-plugin-es_ES.po
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/lang/quick-pagepost-redirect-plugin.pot
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/license.txt
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/page_post_redirect_plugin.php
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/readme.txt
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/tmp-quick-pagepost-redirect-plugin-readme.pot
    # deleted: wp-content/plugins/quick-pagepost-redirect-plugin/tmp-quick-pagepost-redirect-plugin.pot
    # modified: wp-content/themes/startuply-child/style.css
    # modified: wp-content/uploads/sucuri/sucuri-failedlogins.php
    # modified: wp-content/uploads/sucuri/sucuri-lastlogins.php
    # modified: wp-content/uploads/sucuri/sucuri-oldfailedlogins.php
    # modified: wp-content/w3tc-config/master.php
    #
    # Untracked files:
    # (use "git add ..." to include in what will be committed)
    #
    # wp-content/mu-plugins/PluginOrganizerMU.class.php
    # wp-content/plugins/plugin-organizer/
    # wp-content/plugins/strictly-system-check/
    # wp-content/plugins/wp-force-https/
    # wp-content/plugins/wp-staging/
    # wp-content/uploads/wp-staging/
    no changes added to commit (use "git add" and/or "git commit -a")

    A question is whether the repositories will be available if I remove and reinstall revisr. Obviously though I’d prefer a less drastic fix.

    Thakns for your answer, looking forward to your reply.

    Thread Starter terrainnova

    (@terrainnova)

    I’m also quite sure that I keep getting notified about changes in directories I’ve excluded from being checked.

    Anyone else has seen these two issues?

    Thread Starter terrainnova

    (@terrainnova)

    hi @maussoftware, thanks for your reply and sorry for my belated mine. I eventually went for another plugin in all the sites the contact form wasn’t working. Thanks again

    terrainnova

    (@terrainnova)

    Hello,

    I see notifications of file changes for files and directories I have explicitly asked to be excluded from change detection and corresponding notifications. Has anyone seen this? Is it a bug?

    Thanks

    Thread Starter terrainnova

    (@terrainnova)

    Right thanks doing the checks you suggested made me realise a typo. Thanks for that. I’ll get back to you if I encounter further problems but it seems to be working now.

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