After updating the Salient theme, most of the custom CSS I applied through the page builder stopped working. I updated the CSS to match the new class names, but it didn't help (nor did using the !important declaration). Changes I make using the browser's inspect tool work, but applying the same updates in the Custom CSS panel has no effect. However, I have figured out that wrapping the same CSS code in `<style>` tags and placing it in a raw HTML block on the page works fine. Is there something with updating the theme that could be blocking CSS changes from taking effect?
Another user reported the issue to which the developer responded with below:
Unfortunately, i can't seem to access the server using those credentials - is there possibly a location lock which would prevent an IP from the US?
However, I did some further testing in the meantime and believe I found what the issue is. The post ID at the point where WPBakery is looking for the custom meta in the footer is returning the wrong ID. This means that something in the setup is running a query and not resetting the post data.
I edited the function outputPostFooterCustomJs in wp-content/plugins/js_composer_salient/include/classes/core/class-vc-base.php to reset the post data before trying to get the ID and it has corrected the issue:
Click on Image to View Larger
I will report the issue to WPBakery, but ultimately it seems something else in your setup is modifying the query / running a query and not resetting the post data after doing so, so I'm not sure if WPBakery to implement this workaround in the core.
Could you allow us to log in to your website backend dashboard so we can check on this for you more?. We are gonna need the username and password of admin user as well as the login url.
After updating the Salient theme, most of the custom CSS I applied through the page builder stopped working. I updated the CSS to match the new class names, but it didn't help (nor did using the !important declaration). Changes I make using the browser's inspect tool work, but applying the same updates in the Custom CSS panel has no effect. However, I have figured out that wrapping the same CSS code in `<style>` tags and placing it in a raw HTML block on the page works fine. Is there something with updating the theme that could be blocking CSS changes from taking effect?
Hey Again,
Another user reported the issue to which the developer responded with below:
Unfortunately, i can't seem to access the server using those credentials - is there possibly a location lock which would prevent an IP from the US?
However, I did some further testing in the meantime and believe I found what the issue is. The post ID at the point where WPBakery is looking for the custom meta in the footer is returning the wrong ID. This means that something in the setup is running a query and not resetting the post data.
I edited the function outputPostFooterCustomJs in wp-content/plugins/js_composer_salient/include/classes/core/class-vc-base.php to reset the post data before trying to get the ID and it has corrected the issue:
I will report the issue to WPBakery, but ultimately it seems something else in your setup is modifying the query / running a query and not resetting the post data after doing so, so I'm not sure if WPBakery to implement this workaround in the core.
Could you allow us to log in to your website backend dashboard so we can check on this for you more?. We are gonna need the username and password of admin user as well as the login url.
Thanks
ThemeNectar Support Team