Cyan

In regards to forum posts, I don't think it's how people in general expect forums to work and would likely cause confusion. I know the community software we use (IPS/IPB) used to have this option a very long time ago but no longer does. I don't know if it would be the worth the effort to do custom work around this and it's not something I'm hugely thinking of exploring. As for downloads, I will explore the work required and see if I can add it as an option. This would probably work more if the questions asked were Q&A format. A lot of topics in the support forums really don't fit into that paradigm.

Thanks for letting us know. Luckily now the background not loading doesn't mess up the site too much. I don't really know what caused that problem, it looks like somehow the CSS is referencing itself in the link to the background resource? Not entirely sure how that happened, I'm guessing an esoteric race condition or similar, but I've cleared the cache which forces these files to be regenerated and it looks like it's sorted now.

I've just looked under your account and I can't find any pending files. Are you sure it went through correctly and hit submit file at the bottom of the page?

Try clearing your cache. Badly cached JS could have caused the issue.

I can't replicate your issue, even by checking the 'do not remind me this session box'. The file selector appears as normal.

Which file are you experiencing this issue on?

When a moderator approves your file it will become live. We aim to process these within 24 hours, but realistically it depends on the availability of our moderation staff. So anywhere between a few minutes and a week depending on workload and availabilities. You can report your own file after a reasonable amount of time if you think it has gone unnoticed.

We're looking into this and it's on my list of things to do. Thanks for reporting.

Do you mean the warning that shows up when you download scripts/plugins? The content of the notice does not change, but if you really want it to show again, it is stored in your session. Logging out of the site and logging back in will cause this to display again.

The tagline should be a valid short description for your file, 'updated' doesn't meet that criteria. It should be a short one or two line description about what your file is. The tagline is used throughout the site where your file is shown.

It isn't as clear as it could be, but there is an option called 'Discard pending changes' which should have been in the File Actions menu whilst your new version was pending approval.

In your specific case, it looks your file was held for approval as it was a .RAR file that contained two other .RAR files. Our security check process does not support archive recursion, so archives that contain other archives will always trigger our approval process. To prevent this in future, upload multiple archives separately instead of inside another archive.

@GrunteliciousHello, I've added a self-service repair process for this. If you go to your character's LSPDFR Sync profile on the website, you should now see a message saying your character name may be corrupt. Click the 'Fix this' button and you should be walked through our new automatic repair process for this.

Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.

Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.

Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.

This issue is caused by an LSPDFR plugin you've installed that has changed your characters' Persona. Ultimately the damage is done, your characters' Persona will have been altered on your side and then sent to LSPDFR Sync. LSPDFR Sync is showing the old name because we store the character name separately and it is not normally changeable. In a future LSPDFR release, we will prevent plugins from being able to modify this, as this is not what we expect plugins to do with the API. We can, on our side, modify the character data however we cannot continue to do this on a case by case basis. I will see if I can add a process into LSPDFR Sync on the website to automatically fix this.

Can you post your RPH log?

This issue should be fixed now.

I pushed an update yesterday which contained a few bug fixes, one of them was to fix a few issues with author permissions on their own files (their was a bug that caused authors not to be able to download their own hidden files). It looks like I've broken something in the process. I'm looking into it!

The option to mark a file update as minor (and therefore not send notifications) is now fixed.

Your topic has been moved to GTA V Support, this is not LSPDFR related. Please post in the correct location in the future.

Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.

If you feel this topic has been closed in error, please report this post.