Joel R

What's New in Version 3.1.5
Compatibility fixes for IPS 4.1.9+. Fixed forum last post prefix not being updated on topic edit or multimod. Fixed forum tag/prefix settings (particularly 'show as categories') not being loaded on forum index. Fixed potential error on node save/edit from allowed_prefixes field. Fixed potential error on saved action edit. Fixed spaces being ignored in tag cloud 'exclude' field.  
This should resolve most if not all outstanding issues. Please upgrade and try it out. If your problems persist, let me know. I may need more details.

I will try it  

Thank you for updating this plugin.  

I was fine until you went and brought it up.
Nah, it's fine. IPS is of course free to do as they'd like. As long as they do it well. I'd be happy deprecating my app entirely if it's no longer necessary.

Congrats on the release and thank you for maintaining the application.  

A minor fix for you: when you click on the "Update Available!" message via the ACP, it redirects to your devfuse website which does NOT list the latest 2.4.8 version.  It might be better to direct users to the official IPS Marketplace?  
Also, thanks for the latest release and ongoing support.  

I will think about your suggestion. 

I've been debating how to respond to this paragraph for 3 weeks, since the integration / fragmentation between IP.Board and IP.Gallery is truly a perplexing problem for me.  You bring up some questions that I'd like to address, even if I can only begin to scratch the surface.
For my particular community, I genuinely don't have a good reason as to why I still use image-only forums AND still offer IP.Gallery.  I actually have duplicate content areas for TWO subjects in both IP.Board and IP.Gallery (yes, it drives me crazy), and it really just depends upon the uploader where he wants to be (which is why I'm a fan of seamless integration either direction to show media).  
Some general observations, in no particular order:
In general, the forum tends to be the main 'hang out' area with more activity, so it makes sense to offer space there first.  You just don't get the same feeling of 'activity' in IP.Gallery, so members are naturally more attracted to the forums.   Viewing gallery images is more of a solo activity. Forums are great for progressing image topics. where new updates are posted in new replies. Galleries are great for a curated showcase.    My personal difficulty with the enormity of this question - how to consume, view, and share content in a multi-app platform - is how you can change your interaction with the same content through multiple perspectives.  For example, you can interact by publishing module:
IP.Board -- with categories to publish about Content A, Content B IP.Gallery -- with categories to publish about Content A, Content B It's equally valid to interact by theme:
Content A -- with permission to publish to IP.Board, IP.Gallery Content B -- with permission to publish to IP.Board, IP.Gallery  
Ultimately though, I decided a long time ago I shouldn't force my members to choose one app or the other.  IP.Board and IP.Gallery both equally valid places to upload, since they can both still serve the fundamental purpose of being an image container.   

I've been debating how to respond to this paragraph for 3 weeks, since the integration / fragmentation between IP.Board and IP.Gallery is truly a perplexing problem for me.  You bring up some questions that I'd like to address, even if I can only begin to scratch the surface.
For my particular community, I genuinely don't have a good reason as to why I still use image-only forums AND still offer IP.Gallery.  I actually have duplicate content areas for TWO subjects in both IP.Board and IP.Gallery (yes, it drives me crazy), and it really just depends upon the uploader where he wants to be (which is why I'm a fan of seamless integration either direction to show media).  
Some general observations, in no particular order:
In general, the forum tends to be the main 'hang out' area with more activity, so it makes sense to offer space there first.  You just don't get the same feeling of 'activity' in IP.Gallery, so members are naturally more attracted to the forums.   Viewing gallery images is more of a solo activity. Forums are great for progressing image topics. where new updates are posted in new replies. Galleries are great for a curated showcase.    My personal difficulty with the enormity of this question - how to consume, view, and share content in a multi-app platform - is how you can change your interaction with the same content through multiple perspectives.  For example, you can interact by publishing module:
IP.Board -- with categories to publish about Content A, Content B IP.Gallery -- with categories to publish about Content A, Content B It's equally valid to interact by theme:
Content A -- with permission to publish to IP.Board, IP.Gallery Content B -- with permission to publish to IP.Board, IP.Gallery  
Ultimately though, I decided a long time ago I shouldn't force my members to choose one app or the other.  IP.Board and IP.Gallery both equally valid places to upload, since they can both still serve the fundamental purpose of being an image container.   

Suggestion: include Likes in the stream 

There's actually a disconnect among all the content in all the apps but that's a larger discussion. Each app is a silo of information and is a problem that plagues a multi-app community.
The OP brings up a powerful example of a very unique weakness in the IPS suite.  Admins often have a fractured content base because images in IP.Board have no way of relating to images in IP.Gallery. It's a major, fundamental concern that I share as well.  
The OP shared one solution: to combine image content from forums and gallery into user content.  
I'm more a fan of generating a 'virtual' album in IP.Gallery where the images are linked from the forums.  
In any case, the cross promotion of content is one area that IPS hasn't even started to address but is a very real problem on complex multi app communities.  

I'm in the same position as @superj707 where I have forums meant to showcase iimage, and then I have Gallery.  
Since the underlying purpose is the same, the it makes sense to be able to 'push' content into the Gallery.  
There are multiple ways to implement and they're all acceptable.  In fact, the grand variety of ways to combine the two apps is what makes the integration such a fascinating and compelling feature!
- you can define uploads in the forum topic  to go to Gallery
- you can define uploads to be pushed into a virtual album that can be viewed in Gallery as well
- you can define a hybrid where you choose to upload to both Gallery and to My Attachments
- you can simply Insert Album into the forum post 
- you can upload to My Attachments per user, which lends more to a social experience tird around users
- users automatically get a Community Album by default
Etc.  I don't actually care how IPS implements the cross-over promotion (that's what we pay them for, so they can figure it out, right?) So long as they implement something. But right now we have nothing.  
Will it perhaps require expanded permissions of categories and Albums in Gallery? Perhaps.  Admins of users will need to decide if they allow forum uploads (or on a broader scale, if they allow any community image).  Will it also require expanded settings in forum topics or in forum boards? Probably.  
Theres a ton of complexity in this that I can't even begin to understand.  But its in that complexity that there's the most potential for growth and entire sets of new features.  
 

custom-action-recount-the-content-for-a-member.xml

I'm still finding a way to crop.

My problems:
One album with 100 images blows up the Activity Stream.  You get a flood of images, even though it's a single album.* Clicking IP.Gallery image in AS opens up lightbox, even though underlying premise of AS was content discovery and not content interaction.  Shouldn't it open in the IP.Gallery application? A thought regarding Images in an Album: this is the same corollary as many Posts in a Topic, and the concern of the OP.  Users may not want to be notified of each individual content item, but of the content container (eg. Album or Topic) which is far more visually efficient when there are multiple related content items in the same content container.     

What's New in Version 3.1.3   
Released Just now
Fixed possible group error on tag edit in IPS 4.1.4+. Fixed potential errors on node duplication and saving. Fixed an error when adding tags with the mass-add tool. Improved tag manager on IPS 4.1.6+; tags will now be split out by app and area.

My problems:
One album with 100 images blows up the Activity Stream.  You get a flood of images, even though it's a single album.* Clicking IP.Gallery image in AS opens up lightbox, even though underlying premise of AS was content discovery and not content interaction.  Shouldn't it open in the IP.Gallery application? A thought regarding Images in an Album: this is the same corollary as many Posts in a Topic, and the concern of the OP.  Users may not want to be notified of each individual content item, but of the content container (eg. Album or Topic) which is far more visually efficient when there are multiple related content items in the same content container.     

My problems:
One album with 100 images blows up the Activity Stream.  You get a flood of images, even though it's a single album.* Clicking IP.Gallery image in AS opens up lightbox, even though underlying premise of AS was content discovery and not content interaction.  Shouldn't it open in the IP.Gallery application? A thought regarding Images in an Album: this is the same corollary as many Posts in a Topic, and the concern of the OP.  Users may not want to be notified of each individual content item, but of the content container (eg. Album or Topic) which is far more visually efficient when there are multiple related content items in the same content container.     

My problems:
One album with 100 images blows up the Activity Stream.  You get a flood of images, even though it's a single album.* Clicking IP.Gallery image in AS opens up lightbox, even though underlying premise of AS was content discovery and not content interaction.  Shouldn't it open in the IP.Gallery application? A thought regarding Images in an Album: this is the same corollary as many Posts in a Topic, and the concern of the OP.  Users may not want to be notified of each individual content item, but of the content container (eg. Album or Topic) which is far more visually efficient when there are multiple related content items in the same content container.     

Hi!
Like from object,
can be a great feature add ability to change category icon in pages database via category settings.
otherwise, atm, all category contain same icon and this isn't a great view.
i hope this can be implemented in feature release
-
Edit: this can be a good feature also in forum category...
-
regards,
S.N.

There's actually a disconnect among all the content in all the apps but that's a larger discussion. Each app is a silo of information and is a problem that plagues a multi-app community.
The OP brings up a powerful example of a very unique weakness in the IPS suite.  Admins often have a fractured content base because images in IP.Board have no way of relating to images in IP.Gallery. It's a major, fundamental concern that I share as well.  
The OP shared one solution: to combine image content from forums and gallery into user content.  
I'm more a fan of generating a 'virtual' album in IP.Gallery where the images are linked from the forums.  
In any case, the cross promotion of content is one area that IPS hasn't even started to address but is a very real problem on complex multi app communities.  

I'm in the same position as @superj707 where I have forums meant to showcase iimage, and then I have Gallery.  
Since the underlying purpose is the same, the it makes sense to be able to 'push' content into the Gallery.  
There are multiple ways to implement and they're all acceptable.  In fact, the grand variety of ways to combine the two apps is what makes the integration such a fascinating and compelling feature!
- you can define uploads in the forum topic  to go to Gallery
- you can define uploads to be pushed into a virtual album that can be viewed in Gallery as well
- you can define a hybrid where you choose to upload to both Gallery and to My Attachments
- you can simply Insert Album into the forum post 
- you can upload to My Attachments per user, which lends more to a social experience tird around users
- users automatically get a Community Album by default
Etc.  I don't actually care how IPS implements the cross-over promotion (that's what we pay them for, so they can figure it out, right?) So long as they implement something. But right now we have nothing.  
Will it perhaps require expanded permissions of categories and Albums in Gallery? Perhaps.  Admins of users will need to decide if they allow forum uploads (or on a broader scale, if they allow any community image).  Will it also require expanded settings in forum topics or in forum boards? Probably.  
Theres a ton of complexity in this that I can't even begin to understand.  But its in that complexity that there's the most potential for growth and entire sets of new features.  
 

There's actually a disconnect among all the content in all the apps but that's a larger discussion. Each app is a silo of information and is a problem that plagues a multi-app community.
The OP brings up a powerful example of a very unique weakness in the IPS suite.  Admins often have a fractured content base because images in IP.Board have no way of relating to images in IP.Gallery. It's a major, fundamental concern that I share as well.  
The OP shared one solution: to combine image content from forums and gallery into user content.  
I'm more a fan of generating a 'virtual' album in IP.Gallery where the images are linked from the forums.  
In any case, the cross promotion of content is one area that IPS hasn't even started to address but is a very real problem on complex multi app communities.  

Image board owners face a major struggle between forums for images and Gallery. They are disconnected.
For those of us that run image boards IP4.x has some issues I've been thinking over. There is some disconnected logic regarding images. I have boards for posting images but I also want to use gallery. I am going to end up with fragmented content all over the place and no easy way to find content from a specific user.
It's difficult to view IMAGE attachments per user in profile. You can see "posts" or "topics" but not attachments.  If we have boards that are set up for posting images AND Gallery installed there is a logical disconnect.  We end up with some images in the forums and other images in the gallery but no way at all to tie the two together.  (see screen shot, this user has posted MANY images to the forums but under images there isn't anything posted.)  
Recommendation: An option to allow images posted in the forums to automatically be considered part of gallery and be view-able in both places. Forms feeding gallery would avoid any fragmentation or disconnects. Also a place in profile to view "attachments"
 
Note: VB5 actually works by integrating user "image" content in forums or gallery into one single thing. It's one of the few things I really like about VB5. No more fragmentation or struggle between images posted in forums verses gallery

I think the problem is due to the badly cache  I will think about your idea.