Ryan H.

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.

@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.6
Fixed PHP error when creating a new topic. Fixed a potentially missing tag input in certain circumstances.

@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.6
Fixed PHP error when creating a new topic. Fixed a potentially missing tag input in certain circumstances.

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.5
Fixed 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.

I took a stab at this one, but it should be fixed now.
Fixt
--
I just pushed out version 3.0.4 to fix some nagging issues. If your prefix formats didn't carry through the upgrade, you can try running the repair tool now to fix that. If there are no prefixes, it will look for old data. If you created new ones since, remove them for it to run.
Also, I came across a likely bug in the IPS 4.0 tag system affecting certain configurations. Opened a report about it here: https://community.invisionpower.com/4bugtrack/408-cant-post-tags-if-global-mode-is-closed-but-none-defined-r6780/
What's New in Version 3.0.4
Fixed forum 'defined tags' and allowed prefixes inputs not behaving well. Fixed forum 'default prefix' setting defaulting to the wrong value in some circumstances. Fixed blank tags in some circumstances. Fixed search results not linking properly if the content has a prefix. Fixed a permissions error on forum prefix selection. Fixed prefix formatting pre/post fields being required. Added a potential fix for lost data on upgrade via the repair tool.

I took a stab at this one, but it should be fixed now.
Fixt
--
I just pushed out version 3.0.4 to fix some nagging issues. If your prefix formats didn't carry through the upgrade, you can try running the repair tool now to fix that. If there are no prefixes, it will look for old data. If you created new ones since, remove them for it to run.
Also, I came across a likely bug in the IPS 4.0 tag system affecting certain configurations. Opened a report about it here: https://community.invisionpower.com/4bugtrack/408-cant-post-tags-if-global-mode-is-closed-but-none-defined-r6780/
What's New in Version 3.0.4
Fixed forum 'defined tags' and allowed prefixes inputs not behaving well. Fixed forum 'default prefix' setting defaulting to the wrong value in some circumstances. Fixed blank tags in some circumstances. Fixed search results not linking properly if the content has a prefix. Fixed a permissions error on forum prefix selection. Fixed prefix formatting pre/post fields being required. Added a potential fix for lost data on upgrade via the repair tool.

I took a stab at this one, but it should be fixed now.
Fixt
--
I just pushed out version 3.0.4 to fix some nagging issues. If your prefix formats didn't carry through the upgrade, you can try running the repair tool now to fix that. If there are no prefixes, it will look for old data. If you created new ones since, remove them for it to run.
Also, I came across a likely bug in the IPS 4.0 tag system affecting certain configurations. Opened a report about it here: https://community.invisionpower.com/4bugtrack/408-cant-post-tags-if-global-mode-is-closed-but-none-defined-r6780/
What's New in Version 3.0.4
Fixed forum 'defined tags' and allowed prefixes inputs not behaving well. Fixed forum 'default prefix' setting defaulting to the wrong value in some circumstances. Fixed blank tags in some circumstances. Fixed search results not linking properly if the content has a prefix. Fixed a permissions error on forum prefix selection. Fixed prefix formatting pre/post fields being required. Added a potential fix for lost data on upgrade via the repair tool.

I took a stab at this one, but it should be fixed now.
Fixt
--
I just pushed out version 3.0.4 to fix some nagging issues. If your prefix formats didn't carry through the upgrade, you can try running the repair tool now to fix that. If there are no prefixes, it will look for old data. If you created new ones since, remove them for it to run.
Also, I came across a likely bug in the IPS 4.0 tag system affecting certain configurations. Opened a report about it here: https://community.invisionpower.com/4bugtrack/408-cant-post-tags-if-global-mode-is-closed-but-none-defined-r6780/
What's New in Version 3.0.4
Fixed forum 'defined tags' and allowed prefixes inputs not behaving well. Fixed forum 'default prefix' setting defaulting to the wrong value in some circumstances. Fixed blank tags in some circumstances. Fixed search results not linking properly if the content has a prefix. Fixed a permissions error on forum prefix selection. Fixed prefix formatting pre/post fields being required. Added a potential fix for lost data on upgrade via the repair tool.

Yes, to an extent (though note, I haven't tested anything beyond forums, I don't own other apps). All apps that support tags/prefixes should make use of the prefix formatting, and should have the separate prefix dropdown input, no changes needed. They will not have all of the special forum settings (tag mode, default tags/prefix, require, etc). I have plans to extend those settings to all tag-enabled containers, but that will be some time down the road.
The app does not change sorting/filtering options at all. It'll behave the same way it does in a vanilla install. You can click tags and prefixes, and it will take you to a search for all content having that tag/prefix. It will not filter or sort within the forum directly.
This app allows you to override the tag mode on a per-forum basis, so you can have it closed in one place and open in another, and it adds a 'prefixes only' mode. Currently it does not let you change the minimum/maximum tags per forum, but I'll take that into consideration.
Thanks for the feedback.

Correct. Tags and prefixes would be retained, but it would fall back to default settings, and no formatting.

Yes, to an extent (though note, I haven't tested anything beyond forums, I don't own other apps). All apps that support tags/prefixes should make use of the prefix formatting, and should have the separate prefix dropdown input, no changes needed. They will not have all of the special forum settings (tag mode, default tags/prefix, require, etc). I have plans to extend those settings to all tag-enabled containers, but that will be some time down the road.
The app does not change sorting/filtering options at all. It'll behave the same way it does in a vanilla install. You can click tags and prefixes, and it will take you to a search for all content having that tag/prefix. It will not filter or sort within the forum directly.
This app allows you to override the tag mode on a per-forum basis, so you can have it closed in one place and open in another, and it adds a 'prefixes only' mode. Currently it does not let you change the minimum/maximum tags per forum, but I'll take that into consideration.
Thanks for the feedback.

Advanced Tags & Prefixes
For IPS 4.x
This application enhances IPS Community Suite 4's built-in tag and prefix system. It gives you custom styling and fine-grained control over prefixes, plus new settings, enhancements, and helpful moderation tools. Prefixes are explicitly created through the Admin CP, and can be chosen from a separate prefix dropdown when creating a topic or other prefix-enabled content.
View the Marketplace listing for more info and available features.
Please post any questions, feedback, or support issues here in the support thread.
Go to the Marketplace listing

PM, please. I'm at work, so I won't be able to investigate until this evening (another 6 hours or so).
Yes, the topic prefixes are still there. That's good news.

​Then it's a consequence of how it interacts with the IPB framework. Whatever the case, the problem lies within your code and your code is what would have to be adjusted.
I don't want to seem hostile or evasive, it's just not my problem. I can't help you with errors being thrown in your custom code. I don't guarantee that all code will immediately work without modification. I just give you the tools to make it possible.

Just released a new version 3.0.3. Should fix the issues noted above. Thanks Jujuwar. You can download it on the marketplace.
3.0.3 Changelog:
Fixed an error on forum save. Fixed an error on prefix table display, and quick search not working, in some circumstances. Fixed prefix and tag fields allowing invalid characters (", ', <, >).

That's probably correct. There was a list of disallowed characters in 3.x, but I didn't see that for 4.x so I didn't include any such filter. I'll take a closer look at that. Thanks again.
 
I understand, and I expected that kind of feedback. You're right, it is a large increase. The way I see it, the price of the app for 3.x (along with many other resources) was well under value, and that's a hard cycle to break out of. I'm taking this opportunity to do so. If anything, having large-scale applications all over for $20 does a disservice to everyone, by discouraging talented developers from ever getting involved in the first place. The people capable of that kind of work tend to go where their effort is best spent. I also do work for another (much larger) software ecosystem, Magento. Plugins there average around $200 from reputable companies. Not entirely comparable, but still: A very different ballgame.
If someone wants to undercut me, they're always welcome to try. The reality is I spent a lot of evenings for the better part of the last two months putting this together for everyone.
(I'm also hoping it might help curb piracy. I've never seen it so widespread as for IP.Board 3.x. Doesn't make sense. Suppose we'll see.)

​If you could do that, you'd be able to offer something IP.Pages can't easily do, I just got through asking IPS about it for IP.Pages and they said it couldn't be done easily and because it was classified as a customization, they wouldn't / couldn't help me accomplish it. So if you would, look into adding that feature, if it had it, it would make it worth it to me to buy it, since I already have IP.Pages which can do alot and is quite powerful but  lacks any actual documentation, and makes things more complicated than it needs to be, something like your application here would come in handy, if it made things such as that, easy to do.

​Then it's a consequence of how it interacts with the IPB framework. Whatever the case, the problem lies within your code and your code is what would have to be adjusted.
I don't want to seem hostile or evasive, it's just not my problem. I can't help you with errors being thrown in your custom code. I don't guarantee that all code will immediately work without modification. I just give you the tools to make it possible.

​Hmm, okay. That's an easy fix if you're comfortable editing a file by hand:
File applications/easypages/sources/Page/Page.php
    public static $databaseTable    = 'easypages_pages';     public static $databasePrefix    = 'page_';     public static $databaseColumnId    = 'id';     public static $includeInSitemap    = FALSE;          protected static $databaseIdFields = array( 'page_id', 'page_key' );Add the line in the middle with $includeInSitemap, then save, then no more errors.
I'll make sure that's included in the next update. Thanks.

​Reviews and support requests aren't really connected, but okay. I'm at work right now. I'll look at both of these and have an answer for you tonight.
Thanks!

I imagine this has already been stated, but the report center is quite lacking in finesse compared to what it was in 2.3... Two changes in particular that I would like to see made to it:

- The ability to view the report and comments directly from the topic via an AJAX popup, a la warn logs.

- Moving or hiding [spoiler-like] the post in post reports, so that it's not necessary to scroll past the [sometimes multiple-page-long] post in order to see the actual report.


In general, it seems to me that the system as a whole should be more streamlined and conducive to handling reports en masse. The 2.3 application had that; 3.0's doesn't.

I imagine this has already been stated, but the report center is quite lacking in finesse compared to what it was in 2.3... Two changes in particular that I would like to see made to it:

- The ability to view the report and comments directly from the topic via an AJAX popup, a la warn logs.

- Moving or hiding [spoiler-like] the post in post reports, so that it's not necessary to scroll past the [sometimes multiple-page-long] post in order to see the actual report.


In general, it seems to me that the system as a whole should be more streamlined and conducive to handling reports en masse. The 2.3 application had that; 3.0's doesn't.

I imagine this has already been stated, but the report center is quite lacking in finesse compared to what it was in 2.3... Two changes in particular that I would like to see made to it:

- The ability to view the report and comments directly from the topic via an AJAX popup, a la warn logs.

- Moving or hiding [spoiler-like] the post in post reports, so that it's not necessary to scroll past the [sometimes multiple-page-long] post in order to see the actual report.


In general, it seems to me that the system as a whole should be more streamlined and conducive to handling reports en masse. The 2.3 application had that; 3.0's doesn't.

Ok....

You can now set a fixed size for resizing images. So, if you wanted images to be no bigger than 600px wide or 600px tall, you can now do that.

" alt="" class="ipsImage" width="1000px" height="145px">

" alt="" class="ipsImage" width="1000px" height="651px">


I have also added a "save" button into the lightbox which opens the original image in a new window