Hi, I see on WordPress translation 7 entries to translate, but the .pot file have 103 entries.
Can you fix this?
Hi,
I applied a background color with transparency to one page,
But when I click around my site it seems every page has this new background.
I thought it was meant to only edit the page you are styling.
Had to go through revisions to get the content back.
Really handy plugin once I get this sorted.
]]>I love what I’ve seen of your plugin but it’s not saving here. It acts as if it’s saving but I see no changes on the page afterwards and when I restart Stylist for that page again, it’s lost all of it’s settings.
Thanks for your help!
Kermit Woodall
]]>Okay, select a block to style and under Styling. In Margin and Padding any value entered automatically checks All Sides and the setting does affect all the sides.
Is there way way to only enter one side? Say just change bottom and not the other three sides? Or am I just missing the correct technique?
]]>There is no manual for new users… I great reviews but it seems theres no way for new users to understand how does it function…
Thanks
Hi Stylistwp,
How can I donate?
I’d like to support you in this adventure.
We’re small web design team based in Bulgaria and we’d like to help you out with the project.
Let me know if you plan to release a premium version or something like this – we might be your first client ??
Nice product
]]>Fortunately, I reverted back to a slightly earlier revision. That happened twice.
Another issue is that when I styled one particular item (in this case, an info box), it applied that style to other parts of the site that I didn’t want to affect. FYI, I used the custom code feature to create an overlay, but used the plugin options to apply rounded corners.
This plugin has a lot of potential, but I think that Gutenberg and the new blocks created by other plugin makers are still too new and unstable. Once things settle down with Gutenberg, the possibilities will rival those of current page builders.
]]>I am using the latest version on WP5.0.1. I also have the Kadence Blocks installed.
First of all I used the Kadence blocks on a new page and that worked fine, them I clinked on “style this page”, the stylist plugin seemed to take forever to load so I refreshed the page and it loaded second attempt but on load it completely messed up the Kadence block code. I have tried this 3 times and each time the same thing happens.
I recorded a screencast of this issue here. https://www.screencast.com/t/0FCauafl
scorpio
]]>Installed latest version from Add Plugin page to a WP 5.0 installation.
Went into style the page, CSS code is inserted all over the page as text instead of just styles.
Deactivated plugin and the CSS code was still on the page.
Appeared to have created a copy of the Feature block from the “Editor Block” plugin, but converted it to a plain block instead of an EB block.
Ironically, that let me then add
* ?? Issue: FIXED error with standard Media & Text Gutenberg block.
* ?? Improved compatibility with LiveComposer plugin (section id attribute)
* ?? Fixed bug with Atomic Blocks, CoBlocks and Stackable blocks styling.
For instance if I made changes to my template using Stylist plugin but I did’t like what I saved. Is there any way to undo it. I noticed that if I uninstall the plugin things go back to the default template style sheet. Now if I reinstall the Stylist plugin those previous changes are brought back. Where is that data coming from? And is there any way to reset all changes made using Stylist (other than restoring a template backup)?
]]>Hi,
thank you for this very useful tool.
I test it with Elementor, Woocommerce and various themes.
One strange thing : impossible to apply changes on the woocommerce pages when I use the Customify or Astra theme.
Works well with SitePoint Base
Any possible workaround ?
Regards
= 0.2.3 =
* ?? Issue #32: FIXED console error caused by empty background data.
* ?? Issue #33: FIXED console error “r.indexOf is not a function”.
* ?? Improved compatibility with LiveComposer plugin (section id attribute)
* ?? Fixed bug with SiteOrigin CSS plugin elements styling.
* ?? Fixed bug with Gutenberg plugin blocks styling.
* ?? Fixed some compatibility issues with Simple Custom CSS and JS plugin.
* ?? Issue #31: FIXED console error –?only one instance of babel-polyfill is allowed
* ?? Issue #8: FIXED error causing !important!important in css rules.
* ?? Minor compatibility improvements with SiteOrigin CSS, Elementor, Beaver Builder and Gutenberg.
]]>* ?? Fixed an issue preventing styles to apply after the editing mode closed.
* ?? Better compatibility with the latest API changes in the Gutenberg editor.
This is a quick update to fix some bugs and improve Stylist compatibility with old versions of WordPress. It also improve elements styling for other page builders (including Gutenberg, Elementor, Beaver Builder, Visual Composer, Live Composer, and KingComposer).
* ?? Issue #29: IMPROVED color picker to close when clicked outside.
* ?? Issue #28: IMPROVED color picker to make sure it always have HEX mode.
* ?? Issue #27: IMPROVED performance by disabling unwanted calls to the Google Fonts directory without a need.
* ?? Issue #21: IMPROVED the way CSS selector compose the current CSS path. Now it works properly with composed selectors that includes multiply classes or ids.
* ?? Issue #20: IMPROVED the color picker usability by adding extra space arround selecting area. Not it’s easier to customize colors on the edgest of the selecting gradient.
* ?? Issue #30: FIXED broken columns code in new version of Gutenberg.
* ?? Issue #25: FIXED unwanted syles on the editing screen.
* ?? Issue #24: FIXED broken css when theme or page builder render css code inline after our code inserted.
* ?? Issue #19: FIXED Parese error on old servers with PHP version below 5.4.
* ?? Issue #18: FIXED broken app error when CSS selector loose focus without confirmation from the user.
* ?? Issue #17: FIXED error preventing styles to apply when many Gutenberg blocks edited per session.
* ?? Issue #15: FIXED issue with interface jumping in responsive preview mode.
* ?? Issue #10: FIXED fopen: Failed to open stream… on Windows machines
* ?? Issue #9: FIXED Fatal error: Uncaught Error: Call to undefined function wp_doing_ajax() on very old versions of WP.
* ? Issue #13: REMOVED Full Screen mode for better times.
* ?? Add the notice that Code editor is for CSS only. *CSS gets generated by Stylist automaticaly. Advanced users are welcome to add custom CSS for their Gutenberg blocks.*
* ?? Improved compatibility with SiteOrigin CSS by SiteOrigin (so-css) plugin.
* ?? Improved compatibility with Visual CSS Style Editor By WaspThemes (yellow-pencil-visual-theme-customizer) plugin.
* ?? Improved compatibility with Simple Custom CSS and JS by SilkyPress.com (custom-css-js)
* ?? Improved compatibility with Simple Custom CSS By John Regan, Danny Van Kooten (simple-custom-css)
* ?? Improved compatibility with Styles By Paul Clark (styles) plugin.