JohnDar

Thanks for your help Marc, that has worked perfectly. Everything is now in one bucket, except my Gallery images, which I'll tackle a little later.

What should happen when the destination bucket already contains, for example, a sub-directory called "monthly_2018_01" (say, containing Gallery images) and the bucket I am moving (say, containing downloads) also has a sub-directory called "monthly_2018_01"?

I currently have separate buckets for attachments, galley and downloads. What is the contingency for consolidating these? Given that the sub-directories in each are dated, it may not be as simple case of moving the files manually and then changing the path?

One location, such as server/S3 or one bucket path on S3?

I already have individual buckets for Gallery images and attachments set up. They have been on S3 for a few years. At the moment, everything else is saved to the hosting server. Payment Gateways, Product Groups, Product Images, Calendar Event Cover Photos, Downloads Custom Fields, Community Map Custom Marker Fields, Community Map Embedded Preview Image, [Fcontent] Uploaded Images and [Fcontent] Cache Images all save to a single location: /public_html/uploads I'm leaving those alone for the time being. However, Downloads Files and Downloads Screenshot are saved to a /public_html/ipdownloads and /public_html/ipdownloads/screenshots respectively. I wish to transfer these files to S3, leaving everything in /public_html/uploads untouched. I have already created a bucket for these files, so I'm assuming that I'm good to go with this configuration. Is there a potential issue on the horizon with the screenshots directory being nested in the main downloads directory? Should I consider setting up a dedicated bucket for them? Thank you. That sounds like the best option for me. I wasn't aware that there was a choice to run/not run the background move. Could there be issues with permissions if I copy the files over manually? Given the number and size of the files, I'm slightly terrified.

Apologies if this comes across as a bit of a necro-post, but the location seemed appropriate. I'm self-hosted and about to do this for the files associated with Downloads (mainly files for 3D printing objects). While most of the files are just under 10MB, there are a handful of larger files around 80MB in size. Are they going to present a challenge? I have already increased the PHP limit to 512MB, but haven't initiated the transfer yet. Is there anything else I should be checking (or concerned about) before I do this?

I recently needed to sort a lot of downloads (submitted by members) into new sub-categories to make them easier to navigate. There were originally a few hundred in the original category. I created a series of sub-categories, under the first category to move them into. When I came to work through the downloads and select them to move into the new sub-categories, I discovered that if the downloads I ticked were spread over two or more pages, then an error was produced when I tried to move them... I managed to get around this by pinning the downloads first so they were all on the first page. Once grouped, they moved without issue. I suspect this is a bug?

I have the social logos at the bottom of the board. The X logo (black circle,white X) doesn't line up with the others. It's too high. Is this just me? It's the same on the IPS Support theme.

Thank you. 😀 Yes, I have everything I need.

In order to make things as easy as possible for you to test, I just created a dummy account in the 'members' group. Having done that and logged in as that member from the sign in page, I have discovered that the odd error message has been replaced with a much more acceptable, "The page you are trying to access is not available for your account". It looks like the "Before a ticket can be added, you must create at least one department in the AdminCP" message only appears when an admin logs in 'as' a member from the ACP. I (wrongly) assumed that when logging in as a different member via the ACP, that all Board behaviour would mirror that experienced by that member. In this instance, it isn't the case. We live and learn. 🙂

I have one department in my Support configuration and that is for just sales. That's all I need. Prior to the recent update, it wasn't possible for members who had not purchased a product to contact me via the Support system. Now, the Support button seems to be available to everyone and I'm finding that members are using it to send in a broad range of queries (most of which are just questions best asked in the Forums) to attain personal, one-to-one help. Having 'Sales' as the name of the support department doesn't deter them. They just start by saying, "Sorry if this is the wrong place, but..." If I set the Sales support config to force visibility for purchased product support only, that excludes all other members, but the 'New Request' button is still visible and can still be pressed. When someone (without a purchase) presses the 'New Request' button, it produces an error message intended for the admins, "Before a ticket can be added, you must create at least one department in the AdminCP." That's not really something that should be shown to members. Is there a way to restrict access to the support system to just members who have active purchases? Failing that, can the error message be changed to something that members will understand, such as "There are no support departments currently available to you".

All good, following the update. For info, existing attachments remain inaccessible. To make them available to everyone, the posts need to be edited and the attachments removed and then re-added.

Thank you.

Done

Yes, I'll PM you the details