Qubabos

Thanks for posting!

Unfortunately, this issue is beyond the scope of our technical support. 👩‍💻

Our technical support is happy to help you with the Invision Community platform, but we're unable to help with things like server management, theme questions and modifications.

I've moved this to our Community Support area where other Invision Community owners will see it and help where they can.

IPS 4.6.8 is going to remove following extensions:
core/extensions/core/Sitemap/Applications.php core/extensions/core/Sitemap/Profiles.php So if your 3rd party applications or plugins hook into any of these files, please be warned.
 
Everything else 3rd Party related from our changelog:
I'm really excited about the last point.
Now you're be able to set a member group as not deletable, to prevent that a group which is used for member promotions, or which is literally essential for your 3rd party code can be deleted by the admin.
/** * Can this group be deleted? * * @param \IPS\Member\Group $group The group * @return void */ public function canDelete( $group ) : bool { return TRUE; }  
Just a short update after a while:)

yes, it works just fine

check you PM. thanks!

Perfect - I will split them out and add them in on the next bug-fix release.

What's new in 2.3.0
functionality has been extended to the database records in Pages, allowing the hiding of content with the record itself and comments added to that record. What's fixed in 2.3.0
changes made to better handle hiding of images, both remotely linked and uploaded as attachments.  
If anyone has any issues with this then please do not contact me via PM unless requested - use this support topic to report issues.

As far as I can see that is a theme problem. You can try it in the default theme to make sure. 

OK - your call.
Just for the record here - I am offering assistance if you need it but if you want a refund then let me know (you will lose access to the free plugin you received too)

The plugin is now called '(NE) Hide post content from guests', and version 2.0 is now available with quite a few additional features - check it out:
Many thanks to @AlexWebsites for assistance over the past few weeks as development of these new features has been completed and tested out.

it works by this way, thank you  

@Qubabos in the meantime you can always use custom.css to override/force a css change.
Add this to custom.css:
.cc-window { opacity: 1 !important; } That would make the element be completely opaque... change the number as you wish.
Lets see if someone else can confirm the opacity setting is working for them or not.

Well it might be that, no idea I have no experience with cloudflare, and without being able to take a look myself I really don't know how to help you

Try uninstalling the plugin, clearing the cache in the ACP support tool and/or browser, and then reinstall.

Ignore what I said above this. I got it working (lol), I will update a new version later today.

FAIL.
I updated the sheet in the resources folder but for some reason left that one I downloaded incorrectly from the plugins github repository in the css folder. (https://github.com/insites/cookieconsent/)
What's weird is that it was working just fine on my live site.
Thanks. I just updated it to fix that @Qubabos

Look at what is going on there. Instead of CSS, there is a whole website calling Github files and whatnot. It breaks my 4.2 site (I tested it on) completely. It’s not just Pages templates. 
 

I will take a look but it doesn't make much sense for what I've seen so far. When the cookie plugin is enabled, the CSS file that has the style for the "SG_record_image" class is not loaded.
Again, it doesn't make sense to me for now because all my plugin is doing is inserting the code they instruct before the </head> element, it's just passing the plugin settings as the parameters. Maybe there's some conflict between both plugins css sheets. It's not fair to just say "it's the other broken" by the other developer, my plugin works just fine on its own, it would probably do the same if you implement the code manually without a plugin. Anyway, I will take a look later.

That’s expected. The new 4.2 reputation calls aren’t in there. I will update it close to the release of 4.2 and then replace the 4.1 version with the 4.2 version. I can’t do that now of course, or it would break for customers who are not running the 4.2 beta. 

In the future, please ask first to clarify what the intended functionality is and how one can set it up. What you describe here isn’t true and it is not helpful to make false statements in the support topic and cause unnecessary confusion among existing and future customers. 
There is no sub-category view. There is a front page view and a listing view. Both have their own settings. So if you visit a (sub-) category, you can of course have clickable thumbnail (resolution) images there, if both are options are turned on for the listing view and you make sure that you are using the latest templates.
 
The other two points are a matter of opinion. You are free to have yours, but that doesn’t mean there is a lack of “refinement for a paid script” on my part.  

Those are regular H2 headlines using the default link color of your theme. So whatever your link color in your theme is, the SuperGrid templates will use. 

As I said: It get’s the database ID added. That can be 2 or 5 or any other number, depending on the number of databases you already had. Don’t worry about it. It’s a feature, not a bug. :-) 

Yes, that’s the one. There should be 4 SuperGrid templates in the template manager and for the listing view with the 3x3 display of all articles, you would have to change the settings in Supergrid Listing → recordRow

2 settings for every tab will do the job -it will be more flexible in use for other users  thank you  

Updated this file, this should be working now.
Added a setting to choose which usergroups see the message

You can unpack the tar file, upload all files to /applications/featuredcontent/. Then go to url yourdomain.com/admin/upgrade to upgrade the application.