-
Posts
-
I’m using the latest membermouse plugin, and at http://t2virtual.com with the latest wordpress version, latest x version, and cornerstone 1.3.3
The core checkout page and any other page that uses membermouse’s code doesn’t look right at all. In safe mode the checkout page looks great… so in a normal theme membermouse isn’t styled very pretty when it comes to the dynamic checkout page, however when using my x theme the words get big or are cut off, and the form boxes are black due to the container and dark theme background I have the x theme set to. I don’t want to stop using the x theme, and I don’t want to not use membermouse. I’m no good with CSS but i think this is a css conflict of some sort. I tried clicking the css box inside membermouse settings and that didn’t help. It seems like a text size and padding and margin and container and background issue. Is there any way I can make it so that the core pages have a clean blank page to load on with or without my header? Or to force clean css or style the css to fix this? Also, I have seen in few places online code that people have written to create custom checkout pages, after I can fix the styling issue, I’d love to have anything close to the actual checkout page/signup page that the guys use on membermouse’s own checkout page which is this page… https://membermouse.com/checkout/ … the more I can get my page like that the better! 🙂 I’ve seen https://gets.io/plugins/membermouse-checkout-snippets/ is there a resource like this anyone else can find? I’m not sure if this will fix it, I feel like this should be a simple fix for some reason. Here is a link that takes you to a checkout page. http://t2virtual.com/checkout/?rid=p1DNe2 This has been the only thing holding me back from finishing my site and launching my product. I appreciate the help very much. Attached is a picture of what I have going on.
Hi There,
It sounds like you might be having an issue with a third party plugin or script. Regretfully, we cannot provide support for third party plugins or scripts as our support policy in the sidebar states due to the fact that there is simply no way to account for all of the potential variables at play when using another developer’s plugin or script. Because of this, any questions you have regarding setup, integration, or troubleshooting any piece of functionality that is not native to X will need to be directed to the original developer.
Thank you for your understanding.
