Matt Shaw

Hi,

Can you please send the translation files over to [email protected] so I can look into this further?

Thanks!

Thanks for the report. I’ll look into this and see if it can be corrected for next release.

Hi,

Great idea, I’ll look into this for a future release.

In the meantime, there are two workarounds-

1. Use SSH (which doesn’t include the password)
2. Create a dedicated user for Revisr/deployments, and give that user read/write permissions on Bitbucket/Github.

Hi,

Thanks for the feedback! The ajax version will definitely be slower on some sites, but the speed decrease would be most noticeable on sites where the non-ajax version would have likely failed (due to a large database, low memory limit, low max execution time, etc).

That being said, there are definitely some sites that have large databases that have successfully tuned them so they can work with the old, non-ajax version. So I may look into adding a “Disable AJAX?” setting for those looking to get the best speed.

There’s no way to enable cron currently, and so far I haven’t had any plans to add it. I’ll let you know if that changes.

Hi Dave,

I’m not able to replicate. Do you get any errors?

Also, can you please send over a copy of the debug info in the “Help” tab to [email protected] so we can get this figured out?

Thanks!

Hi,

Can you please send over the debug info in the “Help” tab to [email protected]?

Also does the error pop up right away or does it run for a while and then happen?

Let me know, thanks!

Glad to hear it!

Hi S?ren,

Thanks for mentioning the issue with the danish characters, I will try to replicate and see if that can be fixed for the next release.

Can you please clarify this?

* set site_url and home to localhost if the development url is set, otherwise set them to the development url (revisr setting)

If the development URL is set to localhost, it should automatically be replacing all instances of “localhost” to the site URL of the site initiating the pull. Is that not working for you?

Regarding your second point, the next release will stop storing any data in the database (except for the main Revisr activity table on the Revisr dashboard page, which can and should be ignored by not including the wp_revisr table in backups, or by adding to gitignore).

All options, commits, etc. will instead be pulled directly from Git.

That release should be ready within the next week.

Glad it worked well for you, thanks for the review!

Hi All,

I’ve pushed out an update that addresses the WooCommerce conflict mentioned above.

@pclowes While you didn’t have WooCommerce installed, it may be worth a try in case this update resolved a similar conflict with another plugin.

Please open a new thread for any further issues/questions/etc. Thanks!

Hi, just to follow up on this, if you were using WooCommerce, I did find a conflict with WooCommerce that was causing the error you mentioned.

This should be fixed in v1.2.2.

Thanks for the feedback all, I’ve identified a conflict with WooCommerce and will be releasing a fix for that shortly.

Thanks @pclowes, please keep me posted.

Are you running WooCommerce by any chance?

Also do you get any errors in your browser’s JS console? Let me know, thanks!

Hi James,

Thanks for reporting the issue and the additional details.

Please send an email with the debug info to [email protected] so we can look into this further. Thanks!