Ryan H.

Ah, that's my app. The error would seem to be because all of your tags being included have exactly the same number of uses (1?). If you use one again, the error will go away. I'll fix that for next release.

I can look into it, but no promises. Okay, you'll have to contact him then. You might see if there's an update for that plugin available first, if you haven't already.

Thanks for the full error info. Per the stack trace, one of your hooks appears to be causing this error: (lines #2 and then #1) IPS\forums\hook174->form( I don't know what hook or plugin that refers to, you'll have to figure it out. I recommend disabling them gradually until the problem stops. My app isn't causing the error, it's just being given bad data.

I don't know, I don't own blogs. I tried to make it in a way that will support any tag/prefix-capable app, but I can't make any guarantee about that. That shouldn't be necessary. I'll look into that for the next update. Sounds like you got it figured out, though, regardless.

Yes, that would do it. They're not inherited.

I don't know why #2 would be the case, but for #1, realize that you have to define prefixes explicitly before you can add them now. That means creating the prefix, then assigning it anywhere you want it used. Go to ACP > Community > Advanced Tags > Prefixes to start.

That CSS will do the job fine. No, not at this time. I understand the appeal, but it's not an easy thing to accomplish. If nothing else, it would be very liable to cause performance problems. I don't test against every release. That being said, it's unlikely anything broke. If you do find problems, let me know and I'll sort them out.

Not planned. You can set up a 'remove prefix' saved action to get rid of it in that situation, but I can just as well think of situations where that behavior would be desirable.

I've heard the same from someone else, that AT&P prevents saving of some Pages DB settings. I haven't had a chance to investigate further yet, but I will. In the mean time, I'd recommend temporarily disabling the app to make your settings changes, then re-enabling it when you're finished. I know it isn't ideal, but it should work. BomAle, thanks for the info--that should help round it down.

Look at the previous tab, posting settings. There's a field at the bottom to set 'defined tags' for that forum. It's separate from the other AT&P settings because it's a default setting / part of the IPS core. Does that answer your question? I understand. I don't intend to add inline editing like that. However, you can create saved actions to set particular prefixes, and you can easily apply those from the topic view (dropdown) or list (checkboxes).

Look at saved actions.

No, it's all or nothing. Internally, tags and prefixes are treated as basically the same thing.

Do you have the 'Convert all tags to lowercase' setting enabled? That's under System > Settings > Posting > Tags.

Can you send me ACP and FTP access? Without a visible error, and not owning Pages, this is going to be tough for me to chase down. Send through https://privnote.com/ and PM.

I already did, yesterday.

I did something close to #2 for a client on 3.x, a looong time ago. I think it's come up for discussion before--solid idea, great functionality, it's just...complicated. In that case, I basically had to rip out IPS's built-in tag system to make it work. The ad-hoc and unconnected nature of IPS's tag/prefix architecture makes it totally unsuitable for setups like that. It's all using raw text. Anyway, they're good ideas, but I wouldn't expect to see them in the near future.

Just released a minor update. This should fix outstanding issues, at least until the next IPS release is out... @Morrigan, I wasn't able to reproduce your tag cloud issue at all anymore. I can exclude tags with spaces just fine as of 3.1.5. I made an adjustment there anyway, though. What's New in Version 3.1.6 Fixed bugs with editing topic titles. Fixed node settings cache not being cleared on changes (that is, some forum tag/prefix settings not taking effect).

Okay...HeatSeeker reported the same issue above. Like I told him, I'll look into it. Is this you clarifying the issue you posted about above, or something completely different?

You could use multimods to alter the prefix at that point. That's not really a feature I intend to add at this point. Thanks, that helps. I'll look into that further, should be able to find and fix whatever the issue is. Will reach out if I need more info. I'll look into it. I don't have an immediate answer. See comment to Matk above. In what context? I haven't heard of total failure like that from anyone else. Not easily. You can go to the tag management tool in the ACP and delete all tags and prefixes from there; that should do it. Please clarify. I assume the settings are set per 'calendar group'?. If so, no, no workaround for that situation. I'm not sure why they would allow unlinked events like that in the first place. It would be equivalent to posting a topic outside of any forum.

I don't know. From the frontend, I don't see any technical reason why that would be the case--they're both category views, so if it works in one place, it should work in the other, assuming for 'the other' they're actually configured and enabled. I'll be at a conference until late next week, so support will be minimal in the mean time.

Ach. Okay. I know where the problem is for that, anyway.

Works fine for others. What version of IPS, and could you send me the exact URL of the page when you get that error? Did you run the 'recache tags' tool?

Follow-up on this one specifically: I wasn't able to reproduce -- but that could have been related to the search index bug and a broken tag cache. Upgrade, then run the 'recache tags' tool, and see if that fixes it. It should.

What's New in Version 3.1.5 Compatibility fixes for IPS 4.1.9+. Fixed forum last post prefix not being updated on topic edit or multimod. Fixed forum tag/prefix settings (particularly 'show as categories') not being loaded on forum index. Fixed potential error on node save/edit from allowed_prefixes field. Fixed potential error on saved action edit. Fixed spaces being ignored in tag cloud 'exclude' field. This should resolve most if not all outstanding issues. Please upgrade and try it out. If your problems persist, let me know. I may need more details.

I'll look into 1 and 2. 3 is working as expected. The search engine works totally different now; everything is just posts, and IPS does not distinguish between tags and prefixes in any way.