|
Hi, No Problem, just ask for it :) The changed_full already brings a hacked version of the oxcontent smarty plugin that defines a region. Regions can be defined for everything you want, in our demo store i made one for the product description in the details page like this in tabs.tpl: <div class="mercury-region" data-oxcls="oxarticle" data-oxfield="oxlongdesc" data-type="editable" data-oxid="[{$oDetailsProduct->getId()}]">[{oxeval var=$oLongdesc}]</div> These mercury regions can be everywhere and can handle every oxbase entity type, the data-* attributes define these: data-oxcls => the oxbase class name data-oxfield => the field name (will be mapped to long field name automagically) data-type => can be one of these editable or snippetable - editable is default, snippetable allows snippet to be dropped into this region data-oxid => the oxid of the entity that should be modified If you do not want the regions to show up when not in mercury mode you can just surround them with this: [{if $oxcmp_mercury->allowMercury()}] your mercury only markup here [{/if}] I will add this to the homepage, thanks for the suggestion. --
mit freundlichen Grüßen Alexander Kludt  __________________________ Phone: 09283-5925453 Skype: kingschnulli Email: [email protected] Website: www.aggrosoft.de __________________________ Aggrosoft it intelligence GbR Tannstrasse 12 95111 Rehau GERMANY Sitz Rehau, Amtsgericht Hof Steuernummer: 223/165/54508 Ust.-Id. Nr. gemäß § 27 a Umsatzsteuergesetz: DE260722773 ___________________________ Diese Nachricht ist nur für den Empfänger () bestimmt, sollten Sie nicht der Empfänger sein löschen Sie diese Nachricht umgehend und geben Sie uns bitte per Email ([email protected]) Bescheid über den fälschlichen Erhalt.
|
_______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
