bfarber

This issue is resolved for our upcoming 4.6 release.
 

A fix for the issues reported here is pending developer and QA review. Thanks for raising it!

This issue is resolved for our upcoming 4.6 release.
 

I saw this topic and was waiting to see the same thing basically.

This issue is resolved for our upcoming 4.6 release.
 

A fix for the issues reported here is pending developer and QA review. Thanks for raising it!

A fix for the issues reported here is pending developer and QA review. Thanks for raising it!

I saw this topic and was waiting to see the same thing basically.

Yes if your permission setup isn't working as you think it should, I would recommend submitting a ticket so we can help you review it.

There is not, at present, I'm afraid.

If you sort by rating, then we sort by rating (so 5 stars would come before 4 1/2 stars).
I understand what you're describing as a human but this is how the software works I'm afraid.

Do you mean members history logs? If that is what you meant, you can truncate core_member_history table in your database for a quick prunning.
There is also a setting called: Member History under the Profiles tab in the Admin Panel, where you can set it to be prunned automatically based on x amount of days.

Alright, I figured it out. My own Spam assassin rules were working against me. It appears that one of the rulesets that I had enabled was triggering the notification emails to appear like they were spam. I am working on setting a new ruleset up.

Best way to accomplish this is to rebuild Reputation or post counts. It will trigger the group promotions rules for everyone.

If this is for all themes, a plugin which imports your JS is your best bet.
If this is for a specific theme, go to the themes management area in the AdminCP and click the dropdown arrow next to your theme, then choose Manage Resources. Upload the javascript file, and then the table will show you the resource tag to use to point to that file's URL. You can then import this into your template using something like
<script src='{resource...}'></script>  

If this is for all themes, a plugin which imports your JS is your best bet.
If this is for a specific theme, go to the themes management area in the AdminCP and click the dropdown arrow next to your theme, then choose Manage Resources. Upload the javascript file, and then the table will show you the resource tag to use to point to that file's URL. You can then import this into your template using something like
<script src='{resource...}'></script>  

Can you run this sql query:
SELECT filename FROM `core_hooks` WHERE id = 611; That will give you the name of the plugin file that is causing the error.
I do not see anything there indiciating a plugin id to query the core_plugins table btw.

As noted above, it's probably best if you submit a ticket so we can take a look directly.

As noted above, it's probably best if you submit a ticket so we can take a look directly.

As noted above, it's probably best if you submit a ticket so we can take a look directly.

You did not specify these were multiple-GB files. I also would not store those in the database, indeed.
You can store files outside of the web root directory if you write a PHP script as a gateway. Look at /applications/downloads/interface/legacy/screenshot.php and /applications/gallery/interface/legacy/image.php. These are present because 3.x allowed you to store files outside of the web root directory, and upon upgrade we do not move the files to a new location (so a gateway script is necessary to read and print those files out). You just have to enter a custom URL into the file storage handler "http://mysite.com/applications/downloads/interface/legacy/screenshot.php?path=" and then the actual path of the file gets appended to the URL (at which point it is passed as a query string parameter to screenshot.php which does the rest).
In short, this is largely already possible, although I can't say if it's something we want to push to the forefront and make a common feature.

It's far easier for us to advise if we can get in and see your configuration. That said, the legacy handler is never "automatically" used. It was set during a 3.x upgrade in the file storage handler configuration, and if the /screenshots folder (in your case) is web accessible, it should not be necessary. You should be able to edit the storage handler and adjust the "Custom URL" option to remove the PHP loader.

You didn't see this snippet from our 4.6 changelog from me shhhhh
 

You didn't see this snippet from our 4.6 changelog from me shhhhh
 

This is for attachments and will not apply to things like Gallery images or Pages record images (but would apply to attachments in either application, e.g. to comments or the body of a Pages article).
Within Gallery if you change the dimensions of the images to store you will be prompted to rebuild Gallery images

 
Changes to a Pages record image are not retroactive - there is no tool to rebuild the existing thumbnails.