Ryan H.

Does anyone still have the Pages DB saving problem after upgrading to 4.1.13? I heard rumors that the update might fix it. I don't have it to test myself.

Others have reported the same. I'll be looking into it.

4.1.13, or earlier?

I'll look into these issues. May not be until this weekend.

What version of IPB? Do you have prefixes enabled under Posting settings? Is your group allowed to use them?

That happens because there isn't enough variety in your tag cloud (they all have the same occurrences). As soon as one tag occurs more than the rest, the error will go away. I'll fix that for next release.

Only from the ACP.

What do you mean 'it doesn't run the HTML code'?

That probably won't be necessary. I need to try reproducing it still, but I imagine I will be able to. That kind of behavior doesn't surprise me. As for the Pages issues people are having, I've heard rumor that the upcoming 4.1.13 release might address the problem. Can't promise that though.

I'm not sure I follow. Are you saying "staff" was entered both as prefix and tag?

Well, same answer: Prefixes are a core feature too. I can't be sure of how Rules works to say whether it would pick it up with AT&P in place, but I would expect that it should.

Tags are a core feature, so unless you're talking about adding or changing tags through some app-specific feature (saved actions, mass add, tag edit, etc), I would expect it to work--but that's all on the Rules app.

It happens because there isn't enough variety in your tag cloud (they all have the same occurrences). As soon as one tag occurs more than the rest, the error will go away. I'll fix that for next release. First I've heard of such an issue, never seen it myself. It's certainly not intentional, but I can't say much more than that at this point. What version of IPB? How are you moving them? If you run a search reindex, does that fix it? Fine idea, but I'm trying to keep everything app-agnostic. I couldn't add that without making it completely Forum-specific. Doing that for every prefix-capable app in turn is not very practical. Not yet. This is a known bug, see numerous replies on the last page. Until it's fixed, you can temporarily disable AT&P to make any Pages settings changes. Yes. No, it is not "just a sorting thing". I'm not sure I understand. Are you saying, since the search engine already incorporates tags and forums, it should be easy? ...No, the search engine functionality would not help with filtering and sorting a forum. I'm not about to rewrite a fundamental part of the Forum application.

First I've heard of that. I'll look into it.

Are the prefixes assigned to the forum you're posting in? Does your group have access to use them? No, this app does not support multiple prefixes per topic.

Turn off the IPS setting 'Force tags to lowercase', under Posting settings.

Working on it. Others have brought it up too. For now, disable AT&P temporarily to make any Pages changes.

Topic descriptions aren't officially a thing anymore, so no.

Unless you can search for some common text in them with the mass-add tool, no.

I can look into that for a future release, but it's not currently a feature. It would probably be quite a bit more involved than it sounds. Thanks for the rundown. A couple others have reported the same issue. I haven't solved it yet. Until I do, I recommend disabling AT&P temporarily while you need to edit your databases.

No, they're all stored together, but IPS keeps track of where each instance belongs (it has to). I separate them out simply because that could conceivably be useful. Will consider it, not sure how easy IPS would make that. But fair idea.

No, I can't see. What do you mean "forum only show 5"? Did you edit the forum settings? Because the forum is set to require a prefix, and you didn't pick one.

Sorry to hear that. You can try contacting marketplace@invisionpower.com, but as a rule I don't think they give refunds except in extenuating circumstances.

Not out of box. You can edit a tag (and make it multiple words), but not turn one tag into several.

Did you change anything? Like I said, the error is happening because your most-used tag in the widget and your least-used tag in the widget have exactly the same number of uses. From your screenshot, it looks like there's only one with two or more uses. That's why the error is happening.