Do any of you have experience with, and/or can you suggest a use-case for, CMSModule::CreateReturnLink() ?
I'm wondering because the method produces a string with an embedded URL which can be partially-'entitized' (not e.g. urlencoded). I think such anchor would (if actually modified) be unusable verbatim in a browser. Nor would the $onlyhref-returned URL be usable as-is.
Ditto for CMSModule::create_url().
Should we correct something here?
Staus of URL's created in e.g. CMSModule::CreateReturnLink
-
- Forum Members
- Posts: 15
- Joined: Mon Apr 11, 2011 7:33 am
-
- Support Guru
- Posts: 8169
- Joined: Tue Oct 19, 2004 6:44 pm
- Location: Fernie British Columbia, Canada
Re: Staus of URL's created in e.g. CMSModule::CreateReturnLi
I would not use any PHP method for creating a 'link', and consider all of them to be 'legacy code'.
Bettter solution is to to give URL's to smarty and then build the link tag, or whatever else (javascript etc). in the template.
Whether the function is buggy or not is irrelevant. consider that the URL is your 'data' give it to smarty to render it as a link or whatever inside your template.
Bettter solution is to to give URL's to smarty and then build the link tag, or whatever else (javascript etc). in the template.
Whether the function is buggy or not is irrelevant. consider that the URL is your 'data' give it to smarty to render it as a link or whatever inside your template.
Follow me on twitter
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.