"$this->getViewPath();" Broken
Permalink
# On this page:
http://www.concrete5.org/help/building_with_concrete5/developers/th...
# It says:
4. Within your templates, make sure that all images and files in your theme are prefixed with
$this->getViewPath();
# But it doesn't do anything. I used it like this:
This works but I don't know if I should use it:
?? So what's wrong with getViewPath() ?
Thanks for any help.
http://www.concrete5.org/help/building_with_concrete5/developers/th...
# It says:
4. Within your templates, make sure that all images and files in your theme are prefixed with
$this->getViewPath();
# But it doesn't do anything. I used it like this:
<img src="<?php echo $this->getViewPath(); ?>/images/header.png" />
This works but I don't know if I should use it:
<img src="<?php echo $this->getThemePath(); ?>/images/header.png" />
?? So what's wrong with getViewPath() ?
Thanks for any help.
Eh... not sure if that was sarcasm, but just in case it wasn't...
I think if there is documentation available, it would be really nice to be able to trust that it's accurate. If it can't be kept accurate and up to date, it should not be available at all. It's misleading and frustrating.
Documentation should be able to help developers to get things done efficiently. Surely everything can be figured out by checking out the sample files in the installation, but that's just shooting with luck.
Take away the misleading documentation or keep it up to date, please.
I think if there is documentation available, it would be really nice to be able to trust that it's accurate. If it can't be kept accurate and up to date, it should not be available at all. It's misleading and frustrating.
Documentation should be able to help developers to get things done efficiently. Surely everything can be figured out by checking out the sample files in the installation, but that's just shooting with luck.
Take away the misleading documentation or keep it up to date, please.
Anywho, not sure why you made the post, but the ambiguous method-name at least to me seems more viable/correct and certainly more future-proof?
The concrete5 guys really only have to maintain functions in regard to the actual core concrete5 app's functionality, and those can change as long as they make the core work with the new functions, and again only if you have a SLA or something, either way, they can do what they want but they seem really good at maintaining their own api calls, although here it apparently failed ya.
Either way, I wasn't aware of getViewPath and I have only come across getThemePath, the former might be a bit of legacy code?