Dll

Is there a thread, blog post or announcement on this community which doesn't end up with this same circular argument anymore? 
It's very tedious. 
 

The way the gallery upload works, when users upload images they tend to leave the caption empty which defaults to the image filename. This is because the submit images button is active right after upload and no further boxes are displayed unless the user actually manually clicks on the images. This design pretty much urges users to not fill the caption. I would like to either be able to make the caption required or to clearly display its default value before image submission. Any ideas on that?

Honestly, in your case, you may want to think about how you work out the cost of running your site and include the value you place on your time within it. You're obviously not the most technically savvy in terms of running a web server (and I mean zero disrespect in saying that) and seem to spend a lot of time doing things on that side with varying levels of success. So, if you took all of that off of your plate, how much extra value could you add to your site with the additional time which would be available to you? Only you know the answer to that, but I think it's a worthwhile consideration. 
When you say it's slower - bear in mind that on here as an example, you're connecting to the USA, you can have your site hosted in the EU. We fairly recently moved over to the cloud, and like you are UK based with a mostly UK audience and we / our users haven't noticed any speed drop. In fact, it's probably a bit faster than our previous platform. 
People have already covered the third point, but suffice to say we've not missed having FTP access and what have you and have used the pages platform to add an ads.txt file and what have you - it's very straightforward to do. 
I'm not here to pitch the cloud to you, I've no skin in the game so to speak, but based on your posts in here and the struggles you've been having at times, I actually think you could benefit from it. 
 

Honestly, in your case, you may want to think about how you work out the cost of running your site and include the value you place on your time within it. You're obviously not the most technically savvy in terms of running a web server (and I mean zero disrespect in saying that) and seem to spend a lot of time doing things on that side with varying levels of success. So, if you took all of that off of your plate, how much extra value could you add to your site with the additional time which would be available to you? Only you know the answer to that, but I think it's a worthwhile consideration. 
When you say it's slower - bear in mind that on here as an example, you're connecting to the USA, you can have your site hosted in the EU. We fairly recently moved over to the cloud, and like you are UK based with a mostly UK audience and we / our users haven't noticed any speed drop. In fact, it's probably a bit faster than our previous platform. 
People have already covered the third point, but suffice to say we've not missed having FTP access and what have you and have used the pages platform to add an ads.txt file and what have you - it's very straightforward to do. 
I'm not here to pitch the cloud to you, I've no skin in the game so to speak, but based on your posts in here and the struggles you've been having at times, I actually think you could benefit from it. 
 

Welcome to this week's Invision Insight!
How's everyone liking the new look to Gallery?! We want to hear all of your feedback, so please visit this topic and take advantage of the testing phase so we can keep it all centralised for easy reference.
On other news, Live Topics is almost ready for its beta release! In December last year we mentioned this new feature coming to the suite and it is definitely something many communities will benefit from. I promise we will provide more details soon!
 
New Version
We have released a new beta version of Invision Community, 4.7.7 Beta 4.
For those that would like to try the beta on their communities, please follow the link below. Last week I wrote about how you can opt-in to beta releases for both Cloud and self-hosted clients.
As always, please back up your communities before upgrading to any beta releases.
 
GraphQL
The GraphQL API is here!
GraphQL describes itself as a query language for APIs that gives clients the power to ask for precisely what is needed and nothing more.
I won't go into too much detail here of course; but @Daniel F has got you covered and went into great detail to explain this new addition to Invision Community.
 
Recent Event
Our February 2023 Release Chat happened this week, but if you missed it, don't stress as you can watch the recording below. Please post your questions and we'll do our best to answer them.
 
Changelog
Here's what the dev team have been working on over the last seven days:
See you in the community and next week right here for another Invision Insight! I look forward to hearing from you all!
Thank you everyone! 🦘

I'm pretty sure that if you rewrite all the CSS you'll resolve this.

I'm pretty sure that if you rewrite all the CSS you'll resolve this.

It's there for me on the latest version of the software / default theme. 

You don't need an sql query, there's a tool on the members page in the acp to do it.
 

I had something similar happen with one of my other applications and it boiled down to composer issues - which as you can see throughout this forum, I think they are still trying to iron out how they manage their dependencies while allowing 3rd party devs to include their dependencies.

Think you're going to need to compromise somewhere. Either by spending more with either more server power/load balancing or with cloudflare so you can change the cache time to something more acceptable for you.
Or, you're going to have to accept the default cache time or the fact your site is going to crash when it's busy.
Alternatively I suppose you could wait for Leicester to get relegated at the end of the season, then I imagine those busy times may get less frequent 😅

It sounds like you asking for the impossible. You want a cache to save you under high load, but you also don’t want to set the cache to cache times, where it could actually significantly reduce the load. If you can’t compromise on the cache, you probably have to rethink your server setup and move to a setup with load balancing options. A one-server setup, powerful or not, will have its limits. 

The issue with duplicates we can see and will look into. The issue with broken images is unfortunately the operating system, as mentioned. You would need to update the operating system to correct that issue.
Guilty as charged you're honour

He's posting a screenshot from this site @Marc Stridgen - so I think the bugs may still be there in this version. 

Oh great - thank you! Must be a typo on my end. Will go check. Thank you for spotting that. 
 

I don't know if this is a setting you can change, but it's looking for Amazon..co.uk - note the two dots rather than one. Changing that will probably fix it.

Bad for SEO, bad for screen readers, bad for visual clutter, not really a "thing" with modern community platforms.

And mayhap there reaches a point of diminishing returns?
To spend 20 hour to gain .0010ms of responsiveness is honestly ridiculous.  You are NOT on a drag strip against another vehicle.... .there IS a simple point of diminishing returns... and apparently you have MORE than enough extra time to devote to them... Most don't , and honestly do not need to.

No problem. If it makes you feel any better, I didn't realise either 😄

You're right, sorry. I was looking at the auto moderation notification settings.

Thanks for sorting this. Merry Christmas 🎄

The patch for this has now been released. Please visit the support area in your admin CP if you wish to apply the fix for this problem.

We're deploying a patch tomorrow morning to address this issue. Sorry for the inconvenience!

That's quite disappointing to be honest. The December release was supposed to be a minor maintenance update with it being year end / Xmas etc. So to introduce a fairly significant bug with it and then leave it in place over a month isn't ideal.

Actually, I think we're good - we were using smtp credentials rather than the correct user key etc. Seems ok now, I think.