nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

VFE issues

Evani20

I am having an issue with VFE in TS6.7.1 Sp1 in Win OS. Any kind of help will be greatly appreciated.

Here is the scenario:

When a page in TeamSite 6.7.1 has invalid code and the Code Cleaner in VFE was NOT RUN on the page, the page will still be generated. However, when we attempt to edit the page with the invalid code, eWebEditPro will NOT activate – it just shows up as a blank “Content” area. A JavaScript error is thrown (yellow exclamation point) in the browser task bar. Then we need to browse through the file system to open the DCR and edit the DCR directly to find the invalid code.

Find more posts tagged with

Comments

motlnt

I am having an issue with VFE in TS6.7.1 Sp1 in Win OS. Any kind of help will be greatly appreciated.

Here is the scenario:

When a page in TeamSite 6.7.1 has invalid code and the Code Cleaner in VFE was NOT RUN on the page, the page will still be generated. However, when we attempt to edit the page with the invalid code, eWebEditPro will NOT activate – it just shows up as a blank “Content” area. A JavaScript error is thrown (yellow exclamation point) in the browser task bar. Then we need to browse through the file system to open the DCR and edit the DCR directly to find the invalid code.

can you give us an example of 'invalid code', also what kind of javascript error you are getting?.

Faizi

I am having an issue with VFE in TS6.7.1 Sp1 in Win OS. Any kind of help will be greatly appreciated.

Here is the scenario:

When a page in TeamSite 6.7.1 has invalid code and the Code Cleaner in VFE was NOT RUN on the page, the page will still be generated. However, when we attempt to edit the page with the invalid code, eWebEditPro will NOT activate – it just shows up as a blank “Content” area. A JavaScript error is thrown (yellow exclamation point) in the browser task bar. Then we need to browse through the file system to open the DCR and edit the DCR directly to find the invalid code.

Have you using the default Visual Format configuration file (visualformatconfig.xml) or customized one?

Evani20

Thanks to motInt and Faizi for your quick response.

The answer of the first question is, when I said invalid codes, I meant to say HTML codes without some closing tags. Please check the attachment for the screen shot.

The answer of the second question is, we are using customized Visual Format configuration file.

Thanks in advance.

Jamik

if you don't allow code cleanup to run then you will have this problem because you have malformed syntax when the page tries to load and the VFE can't load properly because of the missing end tags. We tell our users to always click the wysiwyg button before clicking next/finish buttons. The other option you have is to do field validation on save and make sure you don't have <table> tags without an end tag.

basically, always make sure you have some kind of code cleanup running be it the VFE or custom code.

I don't know if this bug has been filed with support but I do know it's been around for a long time.

Evani20

Thanks Jamik for your helpful suggestion. Here is my question, is this a bug for TS 6.7.1 only? Because when I do the same process in TS 6.1, it works without even code cleanup running. In TS 6.1, I can atleast open the content area to find out the invalid codes, but in TS 6.7.1 its open with a blank area.

Thanks in advance.

Jamik

Thanks Jamik for your helpful suggestion. Here is my question, is this a bug for TS 6.7.1 only? Because when I do the same process in TS 6.1, it works without even code cleanup running. In TS 6.1, I can atleast open the content area to find out the invalid codes, but in TS 6.7.1 its open with a blank area.

Thanks in advance.

I'm not sure how long ago the problem started but it's definitely an issue in 6.7.1 and in 6.7.2 sp1 (maybe showed up in 6.5 it's been so long since we were on 6.5 though I can't remember). Although, in 6.7.2 sp1 the VFE is easier to clean up it looks like since you still see the field but any fields after the VFE field do not show up still.