Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter boxhamster

    (@boxhamster)

    I just updated to MS 3.4.4, but the problem continues.
    (Note that I have to switch the checkout template on my live website to the PMPro to continue to have functionality). See attached video: https://drive.google.com/file/d/1kR649yeaRKwbJLDesjCbLep3Fhq-g4hj/view?usp=sharing

    I’d be grateful for your help. ??

    Plugin Support mgordonStylemixThemes

    (@mgordon7)

    Hello,

    Thank you for waiting,

    Our dev team updated the theme already, you need to update the theme and recheck again

    Cheers

    Thread Starter boxhamster

    (@boxhamster)

    Thank you for your reply. The theme was also updated yesterday (till I get notification from ThemeForest it takes a good few hours actually). I am on theme 4.8.71 as of yesterday afternoon and the problem persists.

    Note that PMPro still vies the “3.1 Outdated Template <small>Theme: masterstudy</small>” warning.

    Plugin Support Stephan StylemixThemes

    (@stephanstylemixthemes)

    Hello @boxhamster

    Thank you for clarification, kindly note that the issue you encountered has been fixed. So it will work without a problem once we update the templates. It is on testing process and will be updated soon. You can follow Changelog in order to be informed about the updates.

    Thank you again for choosing us,
    Best regards

    Thread Starter boxhamster

    (@boxhamster)

    Hi @stephanstylemixthemes
    Thank you for making changes to this part. I just updated the theme to version 4.8.72.
    I’m afraid though that the issue persists. Tested in FF, Edge and Chrome.
    https://swingdancehome.com/en/membership-account-2/membership-payment/?level=3

    • This reply was modified 1 month ago by boxhamster.
    • This reply was modified 1 month ago by boxhamster.
    Plugin Support James StylemixThemes

    (@jamesstylemixthemes)

    Hello @boxhamster,

    I noticed a code that is not included in our plugin or theme: View here.

    If you customized the page or theme template, please check the code shown in the screenshot. I reviewed our template and plugin but couldn’t find this code. I believe it may have been added by you or by custom plugins on your website.

    Best regards,

    Thread Starter boxhamster

    (@boxhamster)

    I finally found a solution for this problem by myself, after being sent back and forth between PMPro and MSLMS support.
    PMPro said that as I activate the PMPro checkout template and the problem disappears, it has nothing to do with their problem. MSLMS said as above that I somehow modified this template myself. I didn’t and wouldn’t even know how to. I kept searching and searching for where this odd code was from.
    In the end I tested out removing various elements from the page in Elementor and found the solution. Removing the checkout shortcode, saving the page and putting it back again somehow “updated” the code on that page. With that this error disappeared.
    It’s very strange behaviour, but finally solved the issue.

    Plugin Support juliastylemixthemes

    (@juliastylemixthemes)

    Hello @boxhamster ,

    Thank you for sharing your experience with us, and we’re so glad to hear that you’ve found a solution! It’s unfortunate that the issue required such a bit of back-and-forth between PMPro and MSLMS support, but we truly appreciate your persistence in tracking down the cause.

    It’s certainly an odd situation, but we’re glad to know that updating the checkout shortcode in Elementor resolved the issue. Sometimes, page elements or shortcodes can become “out of sync,” and refreshing them can fix unexpected behavior.

    If you encounter any further issues or need additional assistance, please don’t hesitate to reach out. We’re always here to help and ensure everything is working smoothly.

    Thank you again for your patience, and best wishes for the rest of your project!

    Best regards,

    Julia Ten

    Stylemix Support Team

Viewing 8 replies - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.