Wednesday 04 May 2005 8:36:29 pm
Hey. There is no need to beg, in caps no less. Moving on, so the next step is to tell eZ publish about your new custom tag via the settings (ini files). I think you didn't really read the instructions I linked to you. Because the three instructions addressed your missing dependency.
> 3. Add custom tag to content.ini.php > file so it is available to the online editor, if you are using it. [CustomTagSettings]
AvailableCustomTags[]=embed_midi
The only alteration to the above instruction I would suggest is to use the <i>settings/override/content.ini.append.php </i> (override) settings file instead of the <i>settings/content.ini</i> file (you may need to create it, the format will be the same as the <i>settings/content.ini</i> file). Also be sure that you have cleared all of your eZ publish cache (not just the template cache) ./bin/shell/clearcache.sh --clear-all
In hind site, It might be simpler for you to place your custom tag into your primary sitedesign instead of the standard. Though sometimes you have to cut your knuckles learning up on eZ publish before you re-implement your solution cleanly. I only mention this because when you do upgrade eZ publish you will have to track, document and backport these customizations into your future upgraded eZ publish installation. Where as if you were to simply keep your custom tags in your primary sitedesign you would not need to watch these dependencies so closely when you go to upgrade eZ publish. I would store them instead into : <i>design/example_org_user/templates/content/datatype/view/ezxmltags</i> Again, you might need to create the directory structure (above). //kracker Atmosphere : God Loves Ugly
Member since: 2001.07.13 || http://ezpedia.se7enx.com/
|