Jump to content

Emediate

Clients
  • Posts

    364
  • Joined

  • Last visited

  • Days Won

    2

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Everything posted by Emediate

  1. Also now getting this. It started out of nowhere.
  2. Apologies for not updating here. The same day we updated, we also included an additional subforum for Auto Expire. It was my mistake and working as intended - it just had 10+ years of threads to work through. It caught back up eventually! 🙂
  3. Could you perhaps offer your apps via a third party website and we just install/maintain them as "Custom" and not via marketplace. I am seeing many developers moving this way. It would prevent many of us who have invested in this (and other) apps from being essentially now orphaned.
  4. Mine remained after the update. Maybe clear your caches?
  5. Just discovered that after running the latest Invision update on March 7, our auto lock topic is not happening after (14) days as per the setting. Is anyone else running this having any probs since the latest update?
  6. Had a quick look but not exhaustive. Wondering if there is already an app to create sets of Tags? Then the ability to define which subforums use which set of tags, and make it a requirement to select a tag/s from within the set.
  7. Bump - still keen on an alternative to this or someone who can take over the plugin.
  8. Will do. Trying - just waiting on a theme update to ensure compatibility (which could also be the culprit).
  9. Still get this randomly ... but this was more interesting this evening - getting this 4 times as well (as well as the corresponding 4 emails)! Don't know how to reproduce to hone in on any cause if I'm honest.
  10. Not sure if anyone else has raised this. Since the latest update, sometimes when a user (including me) reports a post, it processes it 4 times: It's not consistent and doesn't appear to be a pattern, but I've seen it a handful of times now. And again just now. It's not just Admin usergroup, as I have seen it happen on regular member reports too.
  11. Thanks @Marc Stridgen- any update as yet?
  12. This solved that particular repeated System Log, but only seems to have created a new repeated one: Backtrace Never saw this error before the shift of the datastore to the database.
  13. No problem: https://www.stereonet.com/forums/topic/566505-fanless-roon-rock-serverendpoint-dual-core-16gb/ https://www.stereonet.com/forums/topic/559837-denon-dbp-4010ud/
  14. This is only happening on images that have been "inserted" into the post. If you upload the image as an attachment - but don't insert it, they then display correctly within the post.
  15. @Jim M / @Marc Stridgen - I'm prepared to switch to writing to the db - but just want to confirm there will be no issues with doing this on a ~545,000 Topic and 6,000,000 Post board?
  16. Why would the above apply to just one file of many in the datastore, and not affect any others? Are you suggesting using the database rather than the datastore directory? What are the pros/cons of this? We've never written to the database.
  17. Before I investigate switching the datastore to the database, coming back to the original issue, which still exists ... We have cleared the cache We have emptied the datastore and reset the permissions The exact same file "failed opening ..." comes back instantly. Reluctant to consider it a permissions error or some other problem on our end given the system is writing all other files and filling up the datastore quickly again with no other issues. It's this one particular file it's not happy about, and I can confirm this file does not exist on the server. Any other advice?
  18. We just completed a move from local to Amazon S3, and now "some" images uploaded are broken. Eg: However, when you click on the broken image filename, it opens correctly:
  19. Thanks, @Jim M - it doesn't seem to be causing any performance issues that I can tell. I'll let this process complete, clear the logs, cache and the datastore again, and then reassess. Thanks for your input 🙂
  20. Could it be related at all to moving data storage (for attachments) to Amazon S3? That's been processing for 2.5 days (~80% complete). Yes:
  21. The original problem is back again. It stopped for around 12 hours after clearing the datastore, but is now recording the same error 1-2 times an hour. Any other suggestions?
×
×
  • Create New...