Prefix Essentials featuring auto expiring prefixes and prefix filtering

Prefix Essentials featuring auto expiring prefixes and prefix filtering [Paid] 2.3.6.1

No permission to buy (£25.00)
Maybe i don't know it better?
Is there a really big design problem?

[cats] [dogs] [blue] [red] <= i can choose one!


[cat][red] Lola the red cat!
[cat] [blue] Harry the blue cat

Here i can click [cat] and [blue], then i get all [cat] and/or [blue].

How a user should understand why he can add prefixes for filters with prefixes of threads, but not with the list above?!
 
@Stuart Wright Reporting this quick since you have your dev on right now! Still getting ACP errors. Using 2.6.3 recent update.
View attachment 320943
2.6.3.1 fixes the resource bug you are having above. It's for Xenforo 2.2 only.
Thanks.

Maybe i don't know it better?
Is there a really big design problem?

[cats] [dogs] [blue] [red] <= i can choose one!


[cat][red] Lola the red cat!
[cat] [blue] Harry the blue cat

Here i can click [cat] and [blue], then i get all [cat] and/or [blue].

How a user should understand why he can add prefixes for filters with prefixes of threads, but not with the list above?!
You can filter by one prefix at a time.
Xenforo only has one prefix per thread, so the setup you are describing will not work with prefixes.
If you want to use more than one tag for a thread as per your example above, I suggest you use Xenforo tags rather than prefixes.
 
Hello dear @Stuart Wright


your plugin is causing an error to occur on the console in this way. I would be glad if you fix this with an update.

while the plugin is in a passive state
eklenti yok.webp

while the plugin is active
eklenti aktif.webp


this situation is found on the new topic creation screen in forums that have not been assigned a prefix.

for example, there is no assigned prefix in this forum, and an error appears on the new topic opening screen. https://oltamisina.com/forumlar/olta-misina-kafeterya.38/

The prefix is being used in this forum, and an error does not appear on the new topic landing screen. https://oltamisina.com/forumlar/olta-misina-kullanim-klavuzu.40/

when I put your plugin in the passive position, the problem disappears completely
 
Last edited:
What do you mean by

? Do you mean that no prefixes are allowed in the forum?
No, if you click on the links I sent and look, in one of them I created and used a prefix for the topics, in the other there is none. If you press the "new thread" button in the forum where no prefix is used, you will see that it gives an error if you press F12 on the resulting page. But there is no problem with the forums where the prefix is created and used.

When I put your plugin in passive mode, the problem disappears completely.
 
Last edited:
in forums that have not been assigned a prefix
I don't understand what you mean by this.

No, if you click on the links I sent and look, in one of them I created and used a prefix for the topics, in the other there is none. If you press the "new thread" button in the forum where no prefix is used, you will see that it gives an error if you press F12 on the resulting page. But there is no problem with the forums where the prefix is created and used.

When I put your plugin in passive mode, the problem disappears completely.
I still don't understand what is happening. I can't open the pages in the links as they are not viewable by guests.
Both your captures look the same. You haven't created a thread, yet.
Rather than clutter up this thread, please contact me on m2n.co.uk and I will try to help, but you will need to provide more information because I don't understand what the problem is from what you have posted here.
Thanks.
 
I understand. However, when I uninstall your plugin to test whether the problem is caused by the plugin, there is no problem at all. When I activate your plugin, the problem starts.
 
That's impossible because the latest version is
My point is that I think you are using an old version which causes the prefix_menu.min.js error you referred to in post #270.
I was using an old version and after upgrading to 1.2.1, the error is fixed.
This issue is unrelated to Prefix Essentials. I'm not convinced it's the same issue that you first posted about, though.
 
Last edited:
That's impossible because the latest version is
My point is that I think you are using an old version which causes the prefix_menu.min.js error you referred to in post #270.
I was using an old version and after upgrading to 1.2.1, the error is fixed.
sorry I typed the version incorrectly, I'm using 2.6.4. I will completely uninstall and reinstall your plugin and check it out.
 
Anyway, forget it, I will look for another plugin instead of your plugin. this is not the plugin I'm using Thread Custom Field Extras. that's what I'm telling you about.

Screenshot_1.webp

Anyway, it doesn't matter anymore.
 
Last edited:
View attachment 321716

this is a screenshot from your site. If the prefix is not used in the thread , it prints this error.
That error is caused by Custom Thread Field Extras addon. It was out of date on the M2N site, so I updated to version 1.2.1 which fixed it.
that's what I'm telling you about.
Maybe you thought you were telling me about something else, but the error you reported above is unrelated to Prefix Essentials.
Anyway, forget it, I will look for another plugin instead of your plugin.
Fine. I was trying to help you. It requires more patience from the person trying to fix the error, but you seem to have come to the end of yours so good luck.
 
Back
Top Bottom