HTML Replace Table

[Daniel Petroff]

Hi All

We've been trying to do something using the HTMLConvertTable.txt file and came across some strange behavior.

I am sure the answer to this is very simple but I just cannot seem to find it...

In the txt file I add:

.pdf">    .pdf" class="pdf">

So all I am trying to do is get the class="pdf" inserted in the pdf link in the text field. I also added some special characters like ÿ and € to the text field to test that this works at all.

The result is quite strange. When previewed, the page source shows the changes exactly as I want them. All the special characters get relpaced and so does the string I wanted as per above. However, when publishing the special characters get converted but the .pdf"> stays the same...

Is this because of some process that runs afterwards when publishing that puts it back? Is there something I am missing in the convert settings? I just cannot figure it out...

Any helps would be welcome.

Thanks!

Daneil

[Daniel Petroff]

Thanks, however the strange part is that:

1. It works in Page Preview exactly as I want it.

2. Even when all i want to change is .pdf for .pdfs (no spaces) it still doesn't work.

Because of the first point - I am wondering if it has to do with the fact that the whole link tag is re-rendered after the HTMLConvertTable does its thing so the whole thing is replaced...? And in Preview the order of these events is reversed?

On Mon, Dec 17, 2012 at 10:35 AM, Neil Fegen <n.fe...@gmail.com> wrote:

Hi Daniel

I found this a while ago and reported the issue, and it was confirmed as a bug with ID WSGMS-4924 in July 2010.

Basically, trying to work with spaces in HtmlConvertTable doesn't work...this was the official response:

"HTMLConvertTable functionality is not really meant for this kind of thing, and is not meant to contain spaces in the replacement code - so that kind of explains the problems we are seeing in this ticket. They did say I could

raise a bug for it and they accept it is a valid bug, it will not be addressed as a priority as it is more of a "nice to have" rather than a crucial flaw in product functionality."

As it's been two and a half years, I think you can assume it is not going to be fixed...

Neil 

--
You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/reddot-cms-users/-/97kXvHI8jpwJ.
To post to this group, send email to reddot-c...@googlegroups.com.
To unsubscribe from this group, send email to reddot-cms-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.