October 29, 2020 at 01:06 UTC - Views: 12 #65774WeaverKeymaster
Weaver Xtreme 4.4 users with the woocommerce plugin have triggered a bug. Our apologies for this issue!
Fortunately, the issue does not seem to affect any settings, and simply upgrading to 22.214.171.124 should get things back to normal.
A filename issue with the woocomerce-support.php filename. The accidental renaming of the file happened sometime after we had tested the woo support. Really don’t know how it happened, but was likely related to keeping the 4.4 and the new 5.0 version underdevelopment in “sync”. There has been a phase of adding new 4.4 features that needed to be propagated to the new 5.0 development version. It involved an underscore (_) getting changed to a dash (-).
This issue seems to affect only those using Woocommerce, which is probably why we haven’t been totally flooded with reports.October 29, 2020 at 01:09 UTC - Views: 11 #65775RemusParticipant
Hi! Unfortunately both of the last two versions redirect to 404 when click on Release Notes link.
Other than that, thank you for a new version 😉October 29, 2020 at 05:15 UTC - Views: 5 #65782WeaverKeymaster
Thanks for that report – lost a / when building the address of the readme.txt file. One of the coding changes with Weaver Xtreme 4.4 was using a fairly new WordPress API call for determining the location of theme files. The new method essentially now allows ANY theme file to be included (and thus modified) in a child theme. Before, only some files could be included in a child theme.
So in the process, looks like a trailing / got lost for the readme.txt link. Will fix that for next update, but won’t do that immediately as it is non-critical. But that would also mean that someone would be able to include a custom readme.txt file in a child theme.
- You must be logged in to reply to this topic.