Forums / Setup & design / Still no inline URL?
Edwin Metselaar
Thursday 10 April 2003 6:39:18 am
Hi, I have asked it prviously and no-one knew how to solve it. I am looking for a solution to the 'feature' that every object tag is surrounded with <p> marks. Is there any way around it? Is there a place in the code that says where this is done??I am getting quite desperate that the easiest things are the hardest to accomplish in ezP. The rest of the things seem to work quite nicely, only this rendering is tricky because I see no way to override it.
Thanks, Edwin
Thursday 10 April 2003 6:46:21 am
Hmm, I looked here:
http://www.cleara.com/content/view/full/62/
And what do I see? Inline URL's o other parts of the site. I dive into the source and see: --- is posted in our <a href="/content/view/full/78" >news</a> section.---
In other words: they have a solution right there, although I do not know the underlying code. It might be: --- <link href="/content/view/full/78">news</link>---
So that is what I will try now as well and let you know if I get any further with that.
Thursday 10 April 2003 6:52:07 am
seems to work quite ok - hope it solves all my probs..
Quite silly I didn't try this before.
Paul Forsyth
Thursday 10 April 2003 4:48:06 pm
For the Cleara site, the part you are referring to was a xml datafield attribute that displayed using the standard ez3 templates for that attribute.
I believe there are ways to override the standard ways ez outputs html. Ive not yet tested the following but if you have a look for yourself you may perhaps find what you are looking for within:
~/ez3/design/standard/templates/content/datatype/view/ezxmltages/*
you will see lots of template files such as 'paragraph.tpl' where things like <p>. Either changing entries or putting in overrides (override/templates/content/....) should change the behaviour of your files.
Hope this helps.
Paul
Thursday 10 April 2003 11:34:35 pm
Thanks, I will check it out. I am actually not working on the back end of the site only the front end. I have admin privileges, but every change to templates I have to co-ordinate with a "back end" developer. That makes sure I will not break anything also :-)