Theo
Project Manager
/ Moderator
Oct 29, 2006, 8:24 AM
Post #2 of 6
(1129 views)
Shortcut
|
|
Re: [svsanchez] Artman 2 Placeholders different from V1.xx
[In reply to]
|
Can't Post
|
|
Thanks for posting! Actually, the templates should be automatically converted. There may be a few things that are missed (especially if you're using "ebmedded search.cgi queries" or hard-coded includes to published files), but for the most part, all your templates should have their placeholders and templateCells replaced with new syntax.
If there are things being missed, if you let us know we can see about continuing to improve the import system.
Could you please tell me what the new placeholder names are for the following: $cat_name_he
That would be $category.name:htmlEncoded$. Just like Article Manager 1, html and javascript encoded placeholders are simply the normal placeholder with a placeholder modifier - it's just different syntax for the modifier now, being clearly delineated from its placeholder.
It would be a great idea to point us to a page where we can see all the new placeholders we can use as well as those that have changed names. There are a couple ways to get the placeholders that you need.
1) Put an <!-- templatePlaceholderList --> in the template you're working with and repulish it. This gives you all the placeholders available to that template, grouped by the placeholder's prefix (category., article., etc.).
Note that just like in Artman 1, there are often slightly different placeholders in templateCells than in the rest template (in articlePages, you can only put article placeholders with in the article.row, for example).
2) You can also login to Admin > Database Editor and go to "edit table and fields" for the appropriate section to see a partial list of placeholders, though some of them are system fields and not overly useful in your publishing templates.
Note that to use them in your template, they'll be named according to their table ($article.title$, $category.name$).
I am using <!--#include virtual="$published.categoryBreadcrumb.webpath$" --> which doesn't respect the css style. The content for the breadcrumb template should be imported from your artman 1 version and have the exact same classes. Although it's published now, html-wise it works identically to Article Manager 1: you wrap the breadcrumb include in a span that applies a class to it.
Sounds like you're making progress, but if you're hand-updating every single template element than the upgrade system missed something (or a lot) and we should take a look at that.
Talk to you soon, SVS.
Theo Wiersma
Project Manager
(This post was edited by Theo on Oct 31, 2006, 9:43 AM)
|
Let me know how it goes, and if you need any help with it.