I see also that the notes on EE202 suggest that any modules dependant on the pages module may have issues that will need to be addressed by addon developers. Hope that doesn’t mess things up for you too much.
Not at all 😊 Taxonomy doesn’t use page uri’s the same way the Pages module does, it uses regular template/template_group/url_titles so it’s unaffected.
I have had a feature request to have the uri’s stored using the Pages method, but I’m yet to be convinced of the benefits. I’m not getting too hung up on the uri not reflecting how deep the user is in the site at all. It’s more the interface’s job to communicate this to the user in my opinion.
From experience with the pages module, in some sites I built the uris have gotten ridiculously long.
Plus, this way it’s more ‘native’ allowing you to pass extra segments without breaking the url and having to use workarounds. And, moving a node doesn’t change its uri, and won’t result in broken links on your site.
Any thoughts?
This is looking good and i am very glad to see this released on an open license… congrats… In reference to the pages module, i for one use it in kind of the opposite way. i use it to create short urls for pages - typically things like converting /pagestemplategroup/about_us/ to simply /about/ for example - therefore i do like pages module. However, in your module i thought i saw the option for a hardcoded URL - so i could just enter the pages module uri into this and job done…
if i am mistaken, and did not see a URL override option then this would be handy. often my clients need to ad external links to menus, hence the need to do this.
again though - looks great. thanks.
if i am mistaken, and did not see a URL override option then this would be handy. often my clients need to ad external links to menus, hence the need to do this..
There is a URL Override field in there which does exactly the above - it’s not for assigning an url to the template/url_title in the options above it, which I’m presuming you thought the function was for.
Thanks for the feedback!
Hi Iain, Thanks for the reply, no i assumed it was a full override - therefore if i put in /my-link/ that is all your system would out put. Which is perfect as anyone could manually set this up to match to their pages module setup. Also i assume they would use this as a external link - http://www.domain.com/ - that would not screw anything up i presume?
N
Hey there, Just experimenting with your extension which appears quick and simple and have but a wee question. In the docs you mention you can use the tag: {node_has_children} which is true BUT in an IF statement it passes right thru… ie.
{exp:taxonomy:nav tree_id="2" depth="10" entry_id="{entry_id}"}
{if node_has_children == "yes"}
Has sub
{if:else}
Has no sub
{/if}
{/exp:taxonomy:nav}
Regardless of children or not it always fails (uses the if:else) statement. Basically if it has children I was hoping to add a <h2> class. Am I missing something or is this a limitation of the extension ?
V0.3 is now available for download,
Taxonomy now includes a fieldtype which can be activated when the module is installed, or if you already have the module running go to addons and enable the fieldtype there.
It allows you to add/edit a node directly from the publish page. You just need to add the field, and select which tree the field should be associated with.
I’m sure there will be some bugs, but would love to hear feedback on the fieldtype.
Also, the license has been changed to MIT as requested by a couple of people.
Download from iain.co.nz/taxonomy
thanks @audiopleb
I’ve found a bug when moving a parent node to the bottom of its own branch via the fieldtype, (the move has ‘asking for trouble’ written all over it though)
I’m thinking its the MPTTree class, the developer has noted ‘We need to look into this again to find better ways of dealing with the gaps.’ in the function I’m using to move the node…
I’m finding the whole tree apart from the root node gets wiped out with bizarre lft and rgt values of ‘16777215’
Just a word of warning… I’ll try and look into it further.
ok, decided against the move_node function for now. Makes me nervous.
Instead I’m simply deleting the node, promoting it’s children (if any) and re-inserting.
Seems to have fixed the issue, you can download 0.31
EDIT: Found that moving a node was still bugging out on 0.31, I think 0.32 has fixed those and moving nodes via the fieldtype seems pretty solid.
Would love feedback if anyone has had a chance to play, cheers.
One other thing, the taxonomy system uses the group/template dropdown to do it’s thang but is there anyway of the templates that live within the default group not to use the group in their href ?
My default group is “_static”, using the system when I select “_static/mytemplate” then reference the node_url param, it provides “mysite.com/_static/mytemplate” when it should simply be “mysite.com/mytemplate” as “mytemplate” lives in the default site folder.
Thanks in advance 😊
PS. Let me know when you have a “buy me a beer” link on your site, this thing saved my butt.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.