Ryan H.

I understand what you're saying, and I responded to that specifically. I can't fix your uppercase/lowercase problem without making the system case-insensitive altogether. I can't do that because it would be worse for performance and it could just as well break things for any site relying on the current (case-sensitive) behavior. Would be a breaking change. As for changing from lower- to non-lower, again, use the admin manage tags tool. You can fix each tag/prefix in bulk. Unless you have hundreds of prefixes to go through and correct, it's not going to take you a massive amount of time.

If you have to keep the lowercase setting enabled, like I said, there's a tool to convert everything to lowercase for you. All you have to do is click one button. But I'll see about whether that behavior has changed. I think it probably has to be the way it is, or else matching them up for formatting becomes problematic. If you want the capital letters, your best bet would really be to disable that lowercase setting.

"I would hazard a guess that two of those four global tags have prefixes associated with them, and the other two do not." You say all four have prefixes, but they may not match exactly. See below. Prefixes are case-sensitive. If what is on the topic does not exactly match, it will not be considered the same. It's always been that way. If you want to make things consistent, use the 'Manage Tags' admin tool and edit all instances of one to match the other. Then you have the global tag settings set to force all tags to lowercase. If you do not have it set to force all tags to lowercase, all tags will not be forced to lowercase. That setting is under Posting > Tags. Alternatively, if you want everything to be lowercase (easy way to keep everything consistent), there's an advanced tool in the app to convert all settings and existing tags/prefixes to lowercase as well. What task? I have no idea what would be generating JSON for this app.

Resolved via PM. For anyone else trying to use Easy Pages and IP.Content together, you'll probably run into an FURL conflict. It has to be fixed manually. Here's how: Go to: ACP > Advanced Configuration > Friendly URLsSearch 'pages'.Two results will be for Easy Pages. They will both have 'app=easypages' in the 'Real URL'.Most likely, two or more of the friendly urls share the same pattern. Pick one of the apps to change, edit each entry for that app, and change 'pages' to something else in the friendly URL.

I couldn't reproduce this on 4.0.11. Might have been a core bug since fixed?. I think I have a fix for this now, based on Kevin's guidance. Having trouble with dev mode on the latest version though, so I'm afraid I can't test it properly or build it for release just yet. Okay. It's kind of complicated, but I think it's working as intended. The 'allowed prefixes' and 'defined tags' inputs on forums are one and the same internally. I split them apart on the forum form to try making it easier to understand. If no tags/prefixes are defined explicitly on a forum, it will automatically inherit the global predefined tags (if any). And because tags and prefixes are both stored there, if any of those global predefined tags are set up as formatted prefixes, they will be treated as prefixes. I would hazard a guess that two of those four global tags have prefixes associated with them, and the other two do not. What does that mean for you? You can fix it one of two ways. One, remove the global predefined tags and set them all per content container as needed. Or two, go into those affected forums and either define more proper tags, or change the tag mode there to remove the tag or prefix inputs for that forum. Okay, thanks. That should be fixed for the next update.

Sorry, could you clarify? No prefixes in 'allowed prefixes' on a given forum, but the prefix dropdown still displays on posting? Do you have tags or prefixes disabled there? Do you have global predefined tags? (Do they match?)

I'll look into that, thanks. Could be a general problem. If I can't reproduce it myself, I'll contact you for a copy of your error logs. What version of IPS?

What's shown is what it is. Even if I did add renewal down the line (which I have no intention of doing), that wouldn't affect you if you bought it beforehand.

I can't say how soon that might be. But yes, I'll make sure that's fixed with the next update.

I'll check, but I think that's enforced by IPS. Kind of out of my control unless I make larger changes. If anyone can pinpoint where they're coming from, I'll make sure they're taken care of. I have a couple changes in store already that might help.

You da best. And stateful content creation is silly. Thanks.

I really can't reproduce this at all. Maybe I don't understand what is going wrong for you. Fixed for next release. I could not reproduce this. Fresh install, one prefix, set on the one forum, shows up in the default dropdown. Are you absolutely certain 'vintage' is actually defined as a prefix? Tested and couldn't find any issue, but I added some code to make sure of that regardless. Referring to the Manage Tags section, not the mass-add tags/prefixes tool? That could happen if you change one tag to merge with another (but a topic is tagged with both). Handling that would require a much more complex and intensive process than I'm using right now, which is effectively a find/replace query. By any other means, duplicate tags should be handled fine. Bedtime now, I'm afraid. I'll continue from Angus90's post another day.

I'll investigate. It most likely is coming from my app, not clear to me why that would be though.

If you can identify them in the database, look at table core_tags, column 'prefix' (or such). You can change the values there, and then run the rebuild cache tool in my app.

You want to add min/max tags settings per forum? That's a fine idea, I think someone else has brought that up too. There's a wrinkle that I haven't thought through yet, though. As far as IPS is concerned, the prefix is a tag. That means if you're requiring two tags, they can enter two tags, or one tag and a prefix, and that fills the requirement. It makes for a hairy situation. Not sure. I'll investigate when I have time.

If it doesn't, it should. I'll put that on my list of things to check.

I'll look into that, thanks.

Haven't gotten to you yet, I'll try to do that tomorrow. Wanted to get that other issue fixed quickly, but time is limited with the holiday. FWIW, I think they added the disable mode back in with 4.0.9. Also, try running the fix tool to restore the prefixes.

@Jujuwar @NathanR upgrade to 3.0.6. Should fix your issue. Apologies for that. @GrooveOnBeat I can't reproduce your issue with prefix not showing in title. Works fine for me. Are you sure you have that enabled in settings? @David T. Cole That should be fixed in the last release. Please upgrade. Let me know if it continues. @Joel R I don't have much to go on, but I can assure you the app does not modify that file. Try 3.0.6, it could be related. If not, try to track down your PHP error logs for me. What's New in Version 3.0.6Fixed PHP error when creating a new topic.Fixed a potentially missing tag input in certain circumstances.

I'll try to get a fix for that topic error first thing in the morning. Sorry for the delay, busy day. David, I addressed that in the last update, though you may want to hold off on that for the moment.

I couldn't reproduce this in testing. If you want me to look into it, send me credentials again and I'll get to it when I can. @GrooveOnBeat, all of your issues should be fixed. Thank you. #1 looks like an IPS core bug, but I found a workaround. What's New in Version 3.0.5Fixed JS snippets not being loaded on some admin forms. (You can preview your formatting again! yay! I didn't realize it only worked on my dev site...)Fixed prefix input showing up despite no prefixes being configured.Fixed prefix being added to the tags input on edit.Fixed being unable to save the prefix on a forum if only one prefix exists.Changed 'lowercase' tool to be more exhaustive.

I'll look into those. Thanks for the detailed run-down.

Check capitalization. Does the prefix that's being added exactly match the one you have formatting defined for? It's case sensitive. If you have lowercase tags enabled, that could throw it off. (I don't think you do, but worth mentioning regardless.)

Okay. Could you PM me admin and FTP details to investigate this evening?

No, that shouldn't impact anything. Does anything show up if you click Manage Prefixes? What was the full repair tool response message?