Any Documentation on best methods for customising add-ons?
Permalink 2 users found helpful
Hi all
I just had a support request on one of my add-ons as they clicked update and complained that it override the edits they made to the add-on.
Now I know the 'best practice' is to create a custom template for any add-on you wish to change so when they do get updated it does not affect the amended files.
Is their any documentation on the best practices anywhere on this site so I can point them to it?
Cheers
Chris
I just had a support request on one of my add-ons as they clicked update and complained that it override the edits they made to the add-on.
Now I know the 'best practice' is to create a custom template for any add-on you wish to change so when they do get updated it does not affect the amended files.
Is their any documentation on the best practices anywhere on this site so I can point them to it?
Cheers
Chris
Nice one Chad!
Thanks.
Thanks.
And this works with add ons in (root)/packages as well? What would the /blocks path be for a new view.php for an add on in /packages?
Same thing.
packages/problog/blocks/pro_blog_list/templates/someview/view.php
can be overridden with:
blocks/pro_blog_list/templates/someview/view.php
C
packages/problog/blocks/pro_blog_list/templates/someview/view.php
can be overridden with:
blocks/pro_blog_list/templates/someview/view.php
C
Ahh, key. Thanks for the tip. I think I was trying to do too many directories deep. This is much easier. Cheers!
I have an article here I point all my customers to:
http://stratisdesign.com/stratisdesign/blog/design/custom-block-vie...
ChadStrat