after thinking about it, it should have its own table, and use an unique id as foreign key
that way we don't need to store same value over and over again
this also helps to build a tag suggestion base on existing tags (similar to @ function )
I am about to wrap up a plugin, depending how many ppl interest i might work on it
not terribly hard to have a db field for each post row store hashtags, on clicking returns search result of all post containing the tag
also good idea to add searching weight value to regular search for tags
like i said in previous comment, user define custom action based on the app and target html, for example you can target create post button and supply your custom text as a step, you can rearrange your steps
current 3rd party marketplace ain't structured for collaborative development of multiple dev per resource, if i am going to implement it i rather do it on my own
1st app can be done by temporary storing current redirect and setting redirect to custom url, then proceed with original redirect
2nd app can be done by turning gallery album into page flipper
check and make sure share via email is disabled, attackers use this and then modify the content and title
I got burned after spammer used this 'feature' to sent one million emails, I wish IPS is more open communicating potential loopholes with its customers, even the expired ones
with that said, you may try running sql to clear the backlog in your db
UPDATE files
SET filename = replace(filename,'{','-')
for s3, might be better to write a simple script, get an aws credential,
fetch filename, replace special char then update old key with new key,
aws sdk is widely available for many laguages
don't worry I am just bored of quarantine
for existing files, you can run a query to update db, keep in mind you also need to query update s3 keys as well, prob not hard to do thru aws command line
have a look at /applications/downloads/modules/front/downloads/submit.php
you can prob have a hook to filter out special character in filename before upload, not tested
https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html
if this is what you talking about, you prob want to do some pre processing to alter the file name both in your db and s3 key
if you were using cloudflare before, try clearing cloudflare cache,
i believe there is a constant file setting to set your default site url, i remember looking at db there are secure and non secure url variables,
you should also provide a link to where problem occur to better assist