html open / close

martin75
13 Posts
martin75 posted this 30 November 2016

Dear support,

We use themler to build wordpress themes for our customers. Up till recently no problem, but now we have a problem. For most customers we use visual composer page builder to have optimal flexibility. I think before the last up date we had no problems. What happens? We build the header and footer in themler. Further we define the fonts etc. With visual composer we build the individual pages, which are shown in the content & sidebars area in themler.

Previously we had no problems with editing in visual composer, but now if we update the page it gives an extra first row with [html] and at the end [/html]. Because it places the code in rows it does not apply the css from the theme, that build in themler. The only way to avoid this is with every page you edit to remove these codes before editing from the classic code and put them back in the classic before updating the page. We work with visual composer so that our customers can do the changes to their webiste themselves, but now it is impossible. We can not expect from them to change the classic page code before editing and just also just before updating. Do you know what happened that it does not work any longer?

Dear support, We use themler to build wordpress themes for our customers. Up till recently no problem, but now we have a problem. For most customers we use visual composer page builder to have optimal flexibility. I think before the last up date we had no problems. What happens? We build the header and footer in themler. Further we define the fonts etc. With visual composer we build the individual pages, which are shown in the content & sidebars area in themler. Previously we had no problems with editing in visual composer, but now if we update the page it gives an extra first row with [html] and at the end [/html]. Because it places the code in rows it does not apply the css from the theme, that build in themler. The only way to avoid this is with every page you edit to remove these codes before editing from the classic code and put them back in the classic before updating the page. We work with visual composer so that our customers can do the changes to their webiste themselves, but now it is impossible. We can not expect from them to change the classic page code before editing and just also just before updating. Do you know what happened that it does not work any longer?
Vote to pay developers attention to this features or issue.
13 Comments
Order By: Standard | Newest
Support Team
Support Team posted this 02 December 2016

Hello Martin,
the tags [html][/html] is one of relatively new feature. It i added to content automatically when content is being edited in Themler. They're used to store the content settings like length, bg color, etc.
You may remove these tags manually from WP admin back end, but just keep in mind that if content is edited within Themler the [html] tags are added automatically back.

regards,
Aileen

Hello Martin, the tags `[html][/html]` is one of relatively new feature. It i added to content automatically when content is being edited in Themler. They're used to store the content settings like length, bg color, etc. You may remove these tags manually from WP admin back end, but just keep in mind that if content is edited within Themler the [html] tags are added automatically back. regards, Aileen
martin75
13 Posts
martin75 posted this 02 December 2016

The problem is that Themler in combination with visual composer places the tags back in a new visual composer row. Therefore the css does not work. The only way to avoid this is to remove before editing the tags at the beginning and end and just before updating placing them back. An enormous hassle. Our customers can not update their own text any long, because removing and placing the tags back with every page you edit is to complicated. Is there a a way to disable this new feature, because we will loose customers because of it. Or is there another solution?

The problem is that Themler in combination with visual composer places the tags back in a new visual composer row. Therefore the css does not work. The only way to avoid this is to remove before editing the tags at the beginning and end and just before updating placing them back. An enormous hassle. Our customers can not update their own text any long, because removing and placing the tags back with every page you edit is to complicated. Is there a a way to disable this new feature, because we will loose customers because of it. Or is there another solution?

Last edited 02 December 2016 by martin75

Support Team
Support Team posted this 05 December 2016

Hello Martin,
it'd be helpful if you provide access to your WP admin back end and provide direct link to any page which demonstrates the issue:

Because it places the code in rows it does not apply the css from the
theme, that build in themler.

We'll check would could be done about it

regards,
Aileen

Hello Martin, it'd be helpful if you provide access to your WP admin back end and provide direct link to any page which demonstrates the issue: > Because it places the code in rows it does not apply the css from the > theme, that build in themler. We'll check would could be done about it regards, Aileen
martin75
13 Posts
martin75 posted this 05 December 2016

This is a problem in every theme we use in combination with visual composer.
For instance:

http://pakhetbinnenhofin.nl/wp-admin

Admin
wouteris12a

It occurs on all pages. Try change the h3 line DE OPDRACHT on the following page:

http://pakhetbinnenhofin.nl/de-opdracht/

save it and see what happens or just any other correction on one of the pages. Look how it looks before editing and after.

This is a problem in every theme we use in combination with visual composer. For instance: http://pakhetbinnenhofin.nl/wp-admin Admin wouteris12a It occurs on all pages. Try change the h3 line DE OPDRACHT on the following page: http://pakhetbinnenhofin.nl/de-opdracht/ save it and see what happens or just any other correction on one of the pages. Look how it looks before editing and after.
Support Team
Support Team posted this 07 December 2016

Hello Martin,
it looks like I need additional password to view the page content. Here is what I get

De inhoud is beveiligd met een wachtwoord. Om deze te kunnen bekijken,
vul het wachtwoord hieronder in:

The password "wouteris12a" is not accepted

regards,
Aileen

Hello Martin, it looks like I need additional password to view the page content. Here is what I get > De inhoud is beveiligd met een wachtwoord. Om deze te kunnen bekijken, > vul het wachtwoord hieronder in: The password "wouteris12a" is not accepted regards, Aileen
martin75
13 Posts
martin75 posted this 07 December 2016

ok. To view the page (this is a secret project) use the password: martin

ok. To view the page (this is a secret project) use the password: martin
Support Team
Support Team posted this 08 December 2016

Hello Martin,
I managed to log in and I see the issue. I'll discuss with developers whether it is possible to do anything about it and will let you know

regards,
Aileen

Hello Martin, I managed to log in and I see the issue. I'll discuss with developers whether it is possible to do anything about it and will let you know regards, Aileen
martin75
13 Posts
martin75 posted this 08 December 2016

Thank you in advance,

Martin

Thank you in advance, Martin
Support Team
Support Team posted this 11 December 2016

Hello Martin,
you have added the custom fonts via code

/* Generated by Font Squirrel (https://www.fontsquirrel.com) on November 23, 2016 */
@font-face {
  font-family: 'odin_roundedbold_italic';
  src: url('odin_rounded_-_bold_italic-webfont.woff2') format('woff2'), url('odin_rounded_-_bold_italic-webfont.woff') format('woff');
  font-weight: normal;
  font-style: normal;
}
@font-face {
  font-family: 'odin_roundedregular';
  src: url('odin_rounded_-_regular-webfont.woff2') format('woff2'), url('odin_rounded_-_regular-webfont.woff') format('woff');
  font-weight: normal;
  font-style: normal;
}
...

The files

odin_rounded_-_bold-webfont.woff
odin_rounded_-_bold-webfont.woff2
odin_rounded_-_bold_italic-webfont.woff
odin_rounded_-_bold_italic-webfont.woff2
odin_rounded_-_light-webfont.woff
odin_rounded_-_light-webfont.woff2
odin_rounded_-_light_italic-webfont.woff
odin_rounded_-_light_italic-webfont.woff2
odin_rounded_-_regular-webfont.woff
odin_rounded_-_regular-webfont.woff2
odin_rounded_-_regular_italic-webfont.woff
odin_rounded_-_regular_italic-webfont.woff2

Are added to the theme folder Untitled (that is correct), but they're missed in the folder Untitled_preview .That's why different fonts are used in Themler and live page. Add the listed files to folder Untitled_preview , it resolve the issue.

Regards,
Aileen

Hello Martin, you have added the custom fonts via code /* Generated by Font Squirrel (https://www.fontsquirrel.com) on November 23, 2016 */ @font-face { font-family: 'odin_roundedbold_italic'; src: url('odin_rounded_-_bold_italic-webfont.woff2') format('woff2'), url('odin_rounded_-_bold_italic-webfont.woff') format('woff'); font-weight: normal; font-style: normal; } @font-face { font-family: 'odin_roundedregular'; src: url('odin_rounded_-_regular-webfont.woff2') format('woff2'), url('odin_rounded_-_regular-webfont.woff') format('woff'); font-weight: normal; font-style: normal; } ... The files odin_rounded_-_bold-webfont.woff odin_rounded_-_bold-webfont.woff2 odin_rounded_-_bold_italic-webfont.woff odin_rounded_-_bold_italic-webfont.woff2 odin_rounded_-_light-webfont.woff odin_rounded_-_light-webfont.woff2 odin_rounded_-_light_italic-webfont.woff odin_rounded_-_light_italic-webfont.woff2 odin_rounded_-_regular-webfont.woff odin_rounded_-_regular-webfont.woff2 odin_rounded_-_regular_italic-webfont.woff odin_rounded_-_regular_italic-webfont.woff2 Are added to the theme folder Untitled (that is correct), but they're missed in the folder Untitled_preview .That's why different fonts are used in Themler and live page. Add the listed files to folder Untitled_preview , it resolve the issue. Regards, Aileen
martin75
13 Posts
martin75 posted this 12 December 2016

Dear Aileen,

Thanks, I have copied the files also to the Untitled_preview folder. Any word about the open / close problem?

Dear Aileen, Thanks, I have copied the files also to the Untitled_preview folder. Any word about the open / close problem?
Support Team
Support Team posted this 13 December 2016

Hello Martin,
I suppose that you mean the [html][/html] tags. This won't be changed in the near future. However the provided workaround solves the issue with fonts.
In case you face with other issues please let us know

regards,
Aileen

Hello Martin, I suppose that you mean the `[html][/html]` tags. This won't be changed in the near future. However the provided workaround solves the issue with fonts. In case you face with other issues please let us know regards, Aileen
martin75
13 Posts
martin75 posted this 13 December 2016

Dear Aileen,

I hope you understand that none of our customers can work any longer, as long as the [html] [/html] problem is not fixed.
So we provide them with a site, a content management system for doing the changes to their site. But if they do, they almost need to learn programming because for each thing they need to edit they first have to remove the open / close tags and after editing putting them back before updating the page. And that for each page they need to edit. Unworkable.

This means we have to stop working with themler for our customers or programm a script for each site that solves the problem. Hope that you do not do any new updates with such changes, that causes your loyal customers these problems.
Hope this reply might change your opinion in changing it back.

Dear Aileen, I hope you understand that none of our customers can work any longer, as long as the [html] [/html] problem is not fixed. So we provide them with a site, a content management system for doing the changes to their site. But if they do, they almost need to learn programming because for each thing they need to edit they first have to remove the open / close tags and after editing putting them back before updating the page. And that for each page they need to edit. Unworkable. This means we have to stop working with themler for our customers or programm a script for each site that solves the problem. Hope that you do not do any new updates with such changes, that causes your loyal customers these problems. Hope this reply might change your opinion in changing it back.
Support Team
Support Team posted this 13 December 2016

Hi,

Thanks for your feedback, we'll consider your opinion about the content editor. Sorry to hear that it is such huge inconvenience for you.

Sincerely,
Hella

Hi, Thanks for your feedback, we'll consider your opinion about the content editor. Sorry to hear that it is such huge inconvenience for you. Sincerely, Hella
You must log in or register to leave comments