This topic has 14 replies, 3 voices, and was last updated 8 years, 4 months ago ago by Eva Kemp
Page which have 1 row and 3 columns set from backend editor, but the display in the frontend was terrible. Please advice. I did ask Visual Composer author and ther reply as below
The issue is because there is a Visual Composer related code present in your theme added by the theme author. You will have to get rid of it. I would advise you to do so with the help of theme author, otherwise you might loose the extra elements added by him. Once this is done, you can install the standalone plugin and it will work fine. Kindly check.
Hello,
Please show a page where the issue persists (specify what row you’re talking about) and provide FTP/WP admin credentials in Private Content.
Regards,
Eva Kemp.
Replied in private content
Hello,
Please give us full permissions to wp-admin panel to be able to view all settings.
Also provide FTP credentials.
Regards,
Eva Kemp.
Replied as below
Hello,
IP address has been sent to your mail.
Please check.
Best regards,
Jack Richardson.
Replied below in private
Hello,
Still we can’t view all settings in WP admin panel. Please give us administrator rights. Also we can’t access the files via FTP, there are only 2 folders “sunwayweb” and “aspnet_client”, the “sunwayweb” folder can’t be opened because of the notice “550 Access is denied.”.
So please open accesses for us.
Regards,
Eva Kemp.
Hi. Given full access for the administration panel.
Hello,
Thank you for the access.
The problem was you closed some <div>
in wrong place in your text content.
I’ve edited it.
Clear browser cache and check the page now.
Regards,
Eva Kemp.
is it from code level or from the wp-admin visual composer?
Hello,
The <div>
was added in Visual Composer editor in Text element.
Regards,
Eva Kemp.
Thanks Eva. =D
Hello,
You’re welcome.
Regards,
Eva Kemp.
Tagged: corrupted, editor, frontend, themes, visual compose, woocommerce, wordpress
The issue related to '‘Visual Compose : Frontend Display Corrupted Even BAckend Editor Was Proper’' has been successfully resolved, and the topic is now closed for further responses