teraßyte

Disabling the right click is not an effective way at all. There are countless ways to bypass that limitation (disable javascript, scrape the site, look at the image URL in the page's source, etc.). Personally, I think it's a waste of time even trying. 🙄
 
I'm unaware of any 3rd party plugin that does this, but there are several such examples if you just search for them (Google, Bing, etc). If you still want to go ahead with it, find some JavaScript code and add it to your theme.

Did you specify the $table->rowsTemplate value? 🙂
It's required for a front DB Helpers if I'm not wrong.

You need to establish a connection to the external/remote database you want to use, and then run the queries with the usual framework code to retrieve/display the data:
 
The first codebox shows an example of how to start an external database connection.

When looking at a members profile in acp and selecting the gallery tab it's handy to be able to see their gallery stats but it would also be helpful to see a list of all of their galleries on the same page too, it would make administering galleries and their contents so much easier

Any chance this could be considered in the future ?

You guys should really consider adding a maximum PHP version check both in the suite and the requirements checker. I'm not saying to lock everything with the wrong version, even a simple warning in ACP would to the job.
 
With a simple check for the maximum version, you'd avoid dozens of support requests... 🙄

Yes, you need to add your own API key now. The default API key stopped working almost 1 year ago:

No, you're not missing it. There is no option in Invision Community for that.
 
I've seen modifications to hide images for specific groups, but not based on the member's age if they're logged in.

Yes, you need to add your own API key now. The default API key stopped working almost 1 year ago:

It seems you were excessively helpful. You deserved it twice. 😂

I'm not sure how it happened, but the same user was able to react twice to one of my posts here on this forum:
 
You can see there are 2 Thanks reactions from the same user.
 
I also received 2 separate inline notifications for it.

Hi,
I don't have the answer, but...
I find it interesting that you would use your own editor on a Theme hook. I would agree that using your own editor on a Code hook is far more convenient than using adminCP editor, but for a Theme hook ??? Personally, I find the adminCP editor more convenient as it sorts out all the escapes (among other things). What motivates you to use your own editor?
Secondly, if this used to work before 4.7.16 and if you have NOT made any changes to your editor (either configuration or version update) then I can understand your point of view - that it should not have been broken.
That said, the Invision comments say "do not remove" and that implies "do not modify, either" and your editor has clearly modified the lines - what was '/*comment*/' is changed by your editor to '//comment' which is not the same thing.
John

I usually wait 1-2 weeks after a new release to avoid exactly this kind of issues. The time is usually enough for IPS to release a patch for any major issues.

I usually wait 1-2 weeks after a new release to avoid exactly this kind of issues. The time is usually enough for IPS to release a patch for any major issues.

You guys should really consider adding a maximum PHP version check both in the suite and the requirements checker. I'm not saying to lock everything with the wrong version, even a simple warning in ACP would to the job.
 
With a simple check for the maximum version, you'd avoid dozens of support requests... 🙄

We certainly have, it wasn't quite ready for this release though.

You guys should really consider adding a maximum PHP version check both in the suite and the requirements checker. I'm not saying to lock everything with the wrong version, even a simple warning in ACP would to the job.
 
With a simple check for the maximum version, you'd avoid dozens of support requests... 🙄

In a nutshell...  you want to upload the files to the same spot where you first installed the IPB software into.  We can't tell you EXACTLY where your files are uploaded on your website as it depends on your hosting provider and how they setup their server.  
Here's a little more detail on the process to do a manual upgrade:
- Download the latest version of the IPB software from the client area.  (If you had a legacy migration from another platform, you might need to also check the box to download the converters as well.)
- Extract that ZIP file that is downloaded.  Inside of it will be all of the files related to IPB.
- Launch an FTP application of your choice and connect to your server.  
- Find where your IPB files are installed on the server.  (If you're using a server with cPanel, this is typically inside of the "public_html" folder.)
- Upload all of the extracted files up to your server.  It will prompt you some of the files already exist and what do you want to do.  You will select to OVERWRITE the existing file.  
This process will take a little bit to do.  Once complete, you will visit yoursite.com/admin/upgrade to kick off the upgrader.  It will ask you to login with your ACP credentials and then walk you through the rest of the steps.  

If its not using UTF8MB4 and its converting, then there would be a lot. It may be better to run the converter before you do the upgrade, which you can do from the admin CP in the mysql section

From the js file (line 61):
ips.createModule('ips.ui.uploader', function(){  
To create a new one you need to copy/paste the file in your app, change the name, update the names/references, edit the code you need, and call the new module's name in the HTML.
 
This is the code that registers the module (I'll use the dialog one which is more used):
ips.ui.registerWidget('dialog', ips.ui.dialog, [ 'url', 'modal', 'draggable', 'size', 'title', 'close', 'fixed', 'destructOnClose', 'extraClass', 'callback', 'content', 'forceReload' , 'flashMessage', 'flashMessageTimeout', 'flashMessageEscape', 'showFrom', 'remoteVerify', 'remoteSubmit' ], { lazyLoad: true, lazyEvents: 'click' } ); You need to change the dialog name (maybe dialogbis) which registers the widget. All the other values in the array are the options you can use inline.
 
This is how the code would be with the original dialog module:
<div data-ipsDialog data-ipsDialog-title="TITLE" data-ipsDialog-remoteSubmit data-ipsDialog-flashMessage="ITEM SUBMITTED"> This is how it would look with your updated dialogbis module:
<div data-ipsDialogbis data-ipsDialogbis-title="TITLE" data-ipsDialogbis-remoteSubmit data-ipsDialogbis-flashMessage="ITEM SUBMITTED">  

From the js file (line 61):
ips.createModule('ips.ui.uploader', function(){  
To create a new one you need to copy/paste the file in your app, change the name, update the names/references, edit the code you need, and call the new module's name in the HTML.
 
This is the code that registers the module (I'll use the dialog one which is more used):
ips.ui.registerWidget('dialog', ips.ui.dialog, [ 'url', 'modal', 'draggable', 'size', 'title', 'close', 'fixed', 'destructOnClose', 'extraClass', 'callback', 'content', 'forceReload' , 'flashMessage', 'flashMessageTimeout', 'flashMessageEscape', 'showFrom', 'remoteVerify', 'remoteSubmit' ], { lazyLoad: true, lazyEvents: 'click' } ); You need to change the dialog name (maybe dialogbis) which registers the widget. All the other values in the array are the options you can use inline.
 
This is how the code would be with the original dialog module:
<div data-ipsDialog data-ipsDialog-title="TITLE" data-ipsDialog-remoteSubmit data-ipsDialog-flashMessage="ITEM SUBMITTED"> This is how it would look with your updated dialogbis module:
<div data-ipsDialogbis data-ipsDialogbis-title="TITLE" data-ipsDialogbis-remoteSubmit data-ipsDialogbis-flashMessage="ITEM SUBMITTED">  

From the js file (line 61):
ips.createModule('ips.ui.uploader', function(){  
To create a new one you need to copy/paste the file in your app, change the name, update the names/references, edit the code you need, and call the new module's name in the HTML.
 
This is the code that registers the module (I'll use the dialog one which is more used):
ips.ui.registerWidget('dialog', ips.ui.dialog, [ 'url', 'modal', 'draggable', 'size', 'title', 'close', 'fixed', 'destructOnClose', 'extraClass', 'callback', 'content', 'forceReload' , 'flashMessage', 'flashMessageTimeout', 'flashMessageEscape', 'showFrom', 'remoteVerify', 'remoteSubmit' ], { lazyLoad: true, lazyEvents: 'click' } ); You need to change the dialog name (maybe dialogbis) which registers the widget. All the other values in the array are the options you can use inline.
 
This is how the code would be with the original dialog module:
<div data-ipsDialog data-ipsDialog-title="TITLE" data-ipsDialog-remoteSubmit data-ipsDialog-flashMessage="ITEM SUBMITTED"> This is how it would look with your updated dialogbis module:
<div data-ipsDialogbis data-ipsDialogbis-title="TITLE" data-ipsDialogbis-remoteSubmit data-ipsDialogbis-flashMessage="ITEM SUBMITTED">  

1. Member posting is now working with the latest patch 👍
2. Database records made in clubs do not appear in feeds, not the club feed or the Activity feed. I have seen reactions to records though. 
3. Pages Feed Blocks don’t honor club-level access permissions. On the club level, I turned off access for “Members not in this club” and the records can’t be accessed by non-club-members. But Pages Feed blocks for the database contain these records, despite “honor permission” being activated. The goal here would be to create a “latest news (or whatever the content is) from the clubs I am a member of” block. 
4. Adding a category in a club is missing the Description field
5. Not making a Pages category in a club public leads to a confusing, generic error message, which doesn’t tell the user to join the club to access the content. I think the error should be clearer, or the Pages category tab should be hidden from the club, as it is done with Forums in clubs. Right now, it’s inconsistent. Forum tabs disappear, Pages tabs lead to an error. 

This has now been resolved in the 4.7.16 release. Please update if you are seeing this issue. If you are then still seeing the issue, please let us know.

This is fixed in 4.7.16.

This is fixed in 4.7.16.