Tagged: x
-
AuthorPosts
-
April 12, 2016 at 10:12 pm #879293
ksoupParticipantI have revoked and reassigned about 10 times now (I have three licenses for a wp networked site with three different domains)…. Still get this message
Your code is valid but looks like it has already been used on another site. You can revoke and re-assign within your Themeco account.
Please advise
April 13, 2016 at 7:46 am #879913
JackKeymasterHi there @ksoup,
Thanks for writing in, could you post your purchase code/license please in a private reply please, so we can check.
Also you mention a networked site, so this is a multisite install correct?
Thanks!
April 18, 2016 at 10:35 am #888467
ksoupParticipantThis reply has been marked as private.April 19, 2016 at 3:30 am #889535
JackKeymasterHi there @ksoup,
Thanks for writing back and confirming it is indeed a multisite install.
We’ve been investigating the multisite automatic update issues, validating issue and extension install issue. Our original system was never specifically designed to work with multisite, but would often work when X was active on the main site. The problem is that when WordPress checks for updates at the network level, the theme code isn’t included. With X running on the main site, it will try to insert update information into the WordPress update cache. But that cache is volatile, and the network dashboard can clear it out – at which point because X isn’t running, the X update doesn’t appear anymore and doesn’t validate correctly, thus resulting in error messages and the unlocking of extensions not working.
I’ll check in with the lead developers and see if we’ve made any progress on validation issues within multisite installs.
Would it be possible as well, to get wp-network-admin login details for the multisite install? (In a private reply), that way we can test validating as needed on your sites, without causing delays by having to ask for additional information.
Thank you!
April 19, 2016 at 3:19 pm #890735
ksoupParticipantThis reply has been marked as private.April 20, 2016 at 4:53 am #891500
JackKeymasterHi there @ksoup,
Thanks for writing back!
I’ve done some further testing and it seems to be a incompatibility with the domain mapping. I’ll discuss with the lead developer and keep you up to date.
Thanks!
April 21, 2016 at 12:51 pm #894086
ksoupParticipantSounds good 🙂 Thx
April 26, 2016 at 12:12 pm #900648
ksoupParticipantany news? 🙂
April 27, 2016 at 3:55 am #901697
JackKeymasterHi there @ksoup,
Sorry about the delay on this, I’ve just sent a reminder to the developer to take a look at this. Appreciate your patience! 🙂
June 7, 2016 at 8:33 pm #1031021
ksoupParticipantIt’s been so long, I have forgotten where we are with this. Did you happen to get an answer?
June 8, 2016 at 6:42 am #1031663
LelyModeratorHi There,
This is the response from our developer:
_We’ve been investigating the multisite automatic update issues. Our original system was never specifically designed to work with multisite, but would often work when X was active on the main site. The problem is that when WordPress checks for updates at the network level, the theme code isn’t included. With X running on the main site, it will try to insert update information into the WordPress update cache. But that cache is volatile, and the network dashboard can clear it out – at which point because X isn’t running, the X update doesn’t appear anymore. This is what we’ve deduced about multisite updates being hit or miss. We will likely update our documentation to reflect that automatic updates are not supported on Multisite, but still have a few more things to look into.
-
AuthorPosts
- <script> jQuery(function($){ $("#no-reply-879293 .bbp-template-notice, .bbp-no-topic .bbp-template-notice").removeClass('bbp-template-notice'); }); </script>
