master.js?ver=6.2.0:51 TypeError: Cannot set property ‘status’ of undefined
at master.js?ver=6.2.0:51
at Array.forEach (<anonymous>)
at master.js?ver=6.2.0:51
at e.produce (master.js?ver=6.2.0:20)
at pe (master.js?ver=6.2.0:51)
at master.js?ver=6.2.0:51
at c (master.js?ver=6.2.0:27)
at Generator._invoke (master.js?ver=6.2.0:27)
at Generator.next (master.js?ver=6.2.0:27)
at ke (master.js?ver=6.2.0:51)
Is this a known issue ?
Hi Adam,
Thank you for reporting this issue. It was previously unknown to us.
I am working on this right now and will let you know when I have a fix.
Talk to you soon.
Just to confirm, does this error happen during searching or after you have clicked the “Update Urls” button?
Fantastic thanks so much!
It happens before it seems, it even happens just doing the test after you’ve entered the two urls of the sites to test
If you need to see our admin just let me know
That would actually be really helpful, then I can see exactly what is happening.
I will send you the details privately….
Just to clarify, right this second the new site doesn’t exist in the root of the server which is the destination and where I was running the plugin from when I first encountered the error.
However, it seems when running it from the source original url (that ive shared with you) it’s still largely replicable
Thanks again for letting us see your admin page!
Looking at your site, we were able to locate the issue with the Users section and have implemented a fix.
Version 6.2.1 is now available which will resolve the issue.
Have a great day!
Ah amazing, I will give it a go and clarify if it works.
Just to ask in advance, have you had experience with this theme I’m using called “specular” by codeless.co ? Should I expect any issues with something like this that uses WP Bakery for a lot of it’s content. Will your plugin be able to rewrite urls within this kind of setup ?
Hi Adam,
Certainly, this plugin is fully compatible WP Bakery and content builders of this type. I haven’t had any experience directly with the “specular” theme specifically, but I see no reason why there would be any issues.
As always, if you run into any issues at all, please let us know and we’ll fix them. Our goal (which we have been historically able to reach) is 100% compatibility with every theme and plugin that exists in the WordPress ecosystem.
Hi I’ve tried the move again and it went through without JS errors and did update a lot, however not everything.
I’ve found that buttons created within WP Bakery did not get updated. In the post raw code view mode I can see that they look like this
[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][button title="Lighting Comparison Download" link="/preview/wp-content/uploads/2014/09/Lighting.pdf" new_tab="yes" with_icon_bool="no"][/vc_column][/vc_row]
That /preview part at the start of the link should have been removed.
Hi Adam,
I see from the markup the URL included in the button is relative and does not contain the domain. This plugin has no way to know that
/preview
is part of larger URL (as there could be other instances of/preview
which are not meant to be updated). However, you may update these relative urls by inputting the following values:Have a great weekend!