Current "help.tpl" contains line:

   [{ $oView->getHelpText() }]

In new template this line will be replaced by:

   [{ oxcontent oxid=$oView->getContentId() }]

So if you leave your old template unchanged - help data will be loaded from help templates.
In new version help data will be loaded from defined CMS page by content id.

Currently I'm working on documentation page which will describe the best way of writing help
pages.

Arvydas

--------------------------------------------------
From: "Alexander Kludt" <[email protected]>
Sent: Thursday, June 03, 2010 5:03 PM
To: <[email protected]>
Subject: Re: [oxid-dev-general] Changes in help pages

But what will be the recommended way for creating help pages which ship
with a custom module?
Can you tell me how the system knows what's a help page and what's a
simple CMS content?

Arvydas schrieb:
This fix should not break anything as old "/views/help.php" class
functions will
NOT be changed or removed.

--------------------------------------------------
From: "Alexander Kludt" <[email protected]>
Sent: Thursday, June 03, 2010 4:01 PM
To: <[email protected]>
Subject: Re: [oxid-dev-general] Changes in help pages

Will this break the possibility to supply help pages for custom modules?

Arvydas schrieb:
Hi,

I want to inform, that next release will contain bug #1859 fix
(https://bugs.oxid-esales.com/view.php?id=1859). Fix introduces such
changes:

   - removing of help templates stored in "/help/0/", "/help/1/";
   - storing help content to CMS (Admin > Customer Info >      CMS
Pages);

Old way of help template ("/help/0/", "/help/1/"..) support will be
left.

If you suspect any problems with this change, please inform us.

NOTICE:

If you have old shop version, do not plan to update help pages
administration and struck with character encoding problem, similar to
described in bug entry, please check if your template files are
encoded in expected charset.

Best regards,
Arvydas Vapsva
_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general



_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general

_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general




_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general

_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general

Reply via email to