Hi,
We don’t think our plugin deserves such a negative review, because the CSS styling rule you posted does not affect the whole site. In fact, that styling rule is only inside the apposite CSS file for the wp-admin section of our plugin. The name of the file is correct, but it’s located in the plugin directory /admin/resources/vikrentcar.css while the front-end section of VikRentCar will only load the apposite CSS file located at /site/resources/vikrentcar_styles.css.
We completely agree with what you said about using the !important declaration, but we would like to highlight the fact that we always prefix the CSS selector to avoid conflicts with third-party plugins or with your Theme. The styling rule you posted is an exception, it could definitely be improved by using a better CSS selector, unique for our plugin, but as we said, it is NOT affecting the whole site because we only load that CSS file in the wp-admin section, and only on the pages of our plugin. This means that if you open the WordPress dashboard page, you won’t find that rule or that CSS file in the source code of the page. You will find it only by clicking on our plugin interface.
What’s happening to you is something different. You are using a page-builder plugin while being logged into an administrator account, and the pages of VikRentCar rendered by your page-builder plugin make our framework think that we are in the administrative section of the site (back-end). This is the only reason why that CSS styling rule is disturbing your site, but here again we would like to highlight the fact that if a normal user visited your front-end page, there would not be that disturbing rule, because it’s solely for the wp-admin pages of our plugin.
Unlike many WordPress plugins, ours do not load useless assets on any page of your website. We load an apposite CSS file only on the front-end pages generated by our plugin, and we load an apposite CSS file only in the wp-admin pages of our plugin, not on every possible page.
Our programmers and designers are very careful about not generating conflicts with Themes or other plugins, and that’s why we hope you can change your review score. As we said, we are available to provide a solution for your current situation by using a better CSS selector that only targets those tags when inside a specific container element, but the thing is that your page builder plugin is rendering the wp-admin pages of VikRentCar in the front-end section, and this is wrong. It should be sufficient to edit the pages with Elementor before placing any Shortcode, Block or Widget of our plugin, and only when the page is ready you can add our elements. This way by saving the page, users would not get the back-end CSS styling rules loaded in the front-end pages.
We hope this explains why you are having such issues. We would never put such a generic and invasive CSS styling rule in the front-end section or on any other page with additional contents.
Feel free to get in touch with our team through our website should you have any questions.
Thank you,
The VikWP Team
