- This topic has 8 replies, 3 voices, and was last updated 2 years, 6 months ago by
.
-
Posts
-
Just started trying to use this plugin, what’s the best way to expand the styles from the parent theme?
The SWPM plugin has nothing to do with the WP themes; and is compatible withe the default themes. Is there a specific issue you are having, getting the plugin to work? Also, please review the documentation to better understand how the plugin integrates with WordPress.
https://simple-membership-plugin.com/simple-membership-documentation/For example, here’s a link to a login page: https://test.yogavada.com/login/
As you can see the fields and buttons aren’t pulling in any styles from the parent theme. So I’m just trying to see if there’s a simple solution to have them use the theme’s.
Please refer to the documentation on Miscellaneous CSS Tweaks.
https://simple-membership-plugin.com/miscellaneous-css-tweaks-simple-membership-plugin/So this issue is more than “tweaks” the plugin is meant to adopt the styles of a parent theme. However, it does not do this with the new default WordPress theme.
Hey there,
It doesn’t. I tried with a bunch of block-based themes and it doesn’t appear that it will inherit the input field or button styles for any of them. – Cheers!At this time; I believe there is a “disconnect” between the way SWPM handles styles, and the newer “block theme” styles. This is the best advice I can offer concerning styling of login input fields:
https://simple-membership-plugin.com/forums/topic/customizing-login-form-field-background-color/I will inquire with the developer; to see if there is a path forward.
Just updating the thread to add some clarity for future. The discrepancy arises from the appearance of input buttons within a block that incorporates a unique CSS class. This class is added by the block, and subsequently, the theme applies specific styling to these classes. It’s important to note that these aren’t standard “label” or “Text” elements lacking a distinct CSS definition. Our plugin is designed to remain versatile across various themes.
Incorporating CSS classes from specific themes directly into our plugin’s code is not feasible due to the vast diversity of themes available. Moreover, theme obsolescence over time would introduce dependencies in our plugin’s code on outdated themes. For instance, when our plugin was launched back in 2013, the WP 2013 theme was prevalent, but it’s rarely used today. Our plugin, however, must continue to adapt and remain compatible with the evolving landscape of themes.
- You must be logged in to reply to this topic.