Show Thread Enhancements - Yilmaz - Hide [code,php,html] content from guests (vb5.6.x)

Tested in vbulletin version 5.6.4 works fine

Features:
This mod makes it so you can hide [CODE] [PHP] [HTML] BBcode content from guests
Hide [CODE], [HTML] ve [PHP] from Unregistered/Unverified account.

Description:
This product allows you to decide if you want to hide [CODE], [HTML] and [PHP] BBCode content from Unregistered/Unverified on your site.
Hidden content is replaced by a link to your registration page for guests and a simple message for restricted user groups.

========================================
How to install:
========================================
Upload the content of Yilmaz - Hide [code,php,html] content from guests directory to your root.
that's all it.
enjoy..



Please Mark as Installed if you use this.
Donations always appreciated. :up:


1.3.0
Cache issue fixed

========================================
How to uninstall:
========================================
1. Remove the package "yilmazhidebbcodes" that located in /core/packages/
2. Go to "Manage Products" in the admincp and delete the product named "Yilmaz - Hide [code,php,html] content from guests"

[yilmaz]

Originally Posted by Zweeper

Seems to work now! Good job, nice hack! I keep on testing

Originally Posted by Wayne Luke;n4449447

Do you have "Cache BBCode Render by Usergroup" enabled on your site?

This can help

your-website.ext/admincp/options.php?do=options&dogroup=bbcode

Cache BBCode Render by Usergroup

[Zweeper]

It is working since your last update without the cache bbcode render by usergroup option!

[delicjous]

Great idea, and I respect your work... but I have some concerns.
The way you did the trick wipe out the entire cache every time a user LOOK into any post/ thread. Thats because you emty the cache every time an object of the class of your API-Extension been created/ initialized (thats the way the constructor works). So the forum will never build a cache of any data if any of your hide-mods are installed and that will (probably) affect the entire page speed. #Also if you install more than one of your hide-mods, the database-tables will be emptied for each mod. So if 2 of your mods installed and a user is open 1 thread, post, page.... the entire cache-table-data will be deleted 2 times. There is a table cache and another cacheevent. You comment out the part that emty the cacheevent ... you should delete that also.

If it is ok for you, I will upload a similar mod in the next days/weeks that only delete the cache of the nodes with bbcodes. So the cache works almost normal... and if the option "Cache BBCode Render by Usergroup" is enabled you do not need to delete the cache... so I would select that option to find out if it is necessary to delete the cache of the post.

[yilmaz]

Originally Posted by delicjous

If it is ok for you, I will upload a similar mod in the next days/weeks that only delete the cache of the nodes with bbcodes. So the cache works almost normal... and if the option "Cache BBCode Render by Usergroup" is enabled you do not need to delete the cache... so I would select that option to find out if it is necessary to delete the cache of the post.

@delicjous, thank you for the great suggestion.
I will apply and update the option you said.
Thanks again.


I did as you suggested

PHP Code:

     protected function __construct($nodeid)
     {
         if (vB::getDatastore()->getOption('cachebbcodebyusergroup')==0)
         {
             vB_Cache::resetCache();
             vB::getDatastore()->resetCache();
         }
    } 


[delicjous]

Originally Posted by yilmaz

@delicjous, thank you for the great suggestion.
I will apply and update the option you said.
Thanks again.


I did as you suggested

PHP Code:

     protected function __construct($nodeid)
     {
         if (vB::getDatastore()->getOption('cachebbcodebyusergroup')==0)
         {
             vB_Cache::resetCache();
             vB::getDatastore()->resetCache();
         }
    } 


Thats only a part of my suggestion but even that is more solid than before (recommand if empty because options could be empty!).
Now you have the best solution for users who cachebbcodebyusergroup, but if not cachebbcodebyusergroup the entire cache is still emtied every time a user look into a post. The cache of 30 posts are about 1MB of data, so if you have 30 000 posts and a highly frequented forum you have around 1000 MB data without cache by usergroup, even you use only 5 usergroups the cache could grow fast. So this option is not good for everyone.

[yilmaz]

Originally Posted by delicjous

Thats only a part of my suggestion but even that is more solid than before (recommand if empty because options could be empty!).
Now you have the best solution for users who cachebbcodebyusergroup, but if not cachebbcodebyusergroup the entire cache is still emtied every time a user look into a post. The cache of 30 posts are about 1MB of data, so if you have 30 000 posts and a highly frequented forum you have around 1000 MB data without cache by usergroup, even you use only 5 usergroups the cache could grow fast. So this option is not good for everyone.

You are absolutely right.
The bbcode_code, bbcode_html and bbcode_php templates do not appear in the results.
If it was out, I would replace these templates with other templates.
This topic gives clues. https://vborg.vbsupport.ru/showthread.php?t=327871

[shka]

Another approach: I had created a prototype for zweeper with a frontend controller. This means that the post / bbcode only contains a placeholder and an ajax call, the frontend controller can map any complex (cachable) display logic based on the ajax credentials.

Advantage: No cache reset necessary
Disadvantage: An additional ajax call for each content to be hidden. So only useful for certain constellations (in the case of Zweeper only a hide bbcode in the first post of a thread / blog).

PS @zweeper: Ja du hättest die Tabelle einfach löschen können, nur dann einmalig den Cache leeren.

[Zweeper]

Originally Posted by delicjous

Thats only a part of my suggestion but even that is more solid than before (recommand if empty because options could be empty!).
Now you have the best solution for users who cachebbcodebyusergroup, but if not cachebbcodebyusergroup the entire cache is still emtied every time a user look into a post. The cache of 30 posts are about 1MB of data, so if you have 30 000 posts and a highly frequented forum you have around 1000 MB data without cache by usergroup, even you use only 5 usergroups the cache could grow fast. So this option is not good for everyone.

So that actually can cause my servers RAM usage grow high, right? because I think i just experience that.

[Zweeper]

Originally Posted by shka

Another approach: I had created a prototype for zweeper with a frontend controller. This means that the post / bbcode only contains a placeholder and an ajax call, the frontend controller can map any complex (cachable) display logic based on the ajax credentials.

Advantage: No cache reset necessary
Disadvantage: An additional ajax call for each content to be hidden. So only useful for certain constellations (in the case of Zweeper only a hide bbcode in the first post of a thread / blog).

PS @zweeper: Ja du h?ttest die Tabelle einfach l?schen k?nnen, nur dann einmalig den Cache leeren.

And it still works greate

[delicjous]

All of you should vote for this bug-/ featurerequest-reports:

https://tracker.vbulletin.com/vbulle...sues/VBV-17825
https://tracker.vbulletin.com/vbulle...ssues/VBV-5356

Delete the cache always rise server-usage and will slow down the page. Means it must be possible to modify the content on presentationlayer and not behind the scenes. Right now ...
1. cache have to be cleaned (fully or like I do/ did for the post with bbcode in it) = first database action
2. modify the post content (all in php and only a little serverpower needed)
3. build new cache (for the one post or in this mod fully) = second database action

If the cache emtied fully the entire cache of all post, stylevars, styles ... builds up every pageview.