Jump to content

Tom_F

Clients
  • Posts

    811
  • Joined

  • Last visited

 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 Tom_F

  1. Here is a test thread where I used a test account tomf_test and just any tweet would show blank after showing in preview unless I enabled html for the standard group called ‘members’ https://www.otib.co.uk/index.php?/topic/216941-tweets-not-showing/#comment-4374328 I do not have mod security or varnish, no
  2. Ok I can post as a stock member if I enable HTML posting. So is going awol from preview to post.
  3. I can't see anything that's unusual. I don't have admin on the word filter bypass so I'm not sure that is causing issues. When the users post the source code is looking like this: [code] <div class="ipsEmbeddedOther"> <iframe allowfullscreen="" data-controller="core.front.core.autosizeiframe" data-embedid="embed4364228183" scrolling="no"></iframe> </div> <p> &nbsp; </p> [/code] ^ I just tried it on a test member account and replicated the issue.
  4. Access details are up to date but access is only from IP's I was given for IPS - a 144.x.x.x address and 50.x.x.x address
  5. Really strange one this - members post a link to a tweet, they show in preview but when submitting they don't and get a blank post. However when I do it as admin it shows/works fine.
  6. Yep not sure what happened but re ran the upgrade and all fine
  7. ^ I actually got same error, can you advise best means of fixing.. I tried manual file download and copying over but then when the upgrader runs it still kicks out that error.
  8. Sorry to chase but any update?
  9. This is still sort of an issue, is there a way to reduce the size of the button?
  10. Just to confirm further to the above thread, notifications working fine with no errors!
  11. Hi Marc, I actually followed that link after posting and added in the environmental variable/rebooted and it seems to have created the key now
  12. I get this error going to the support page and I click on the error I get the additional error: 2C338/4 Could not create push notification keys. Error returned: Unable to create the key
  13. Hmm so my 6 monthly fee of $60 has now gone to an annual fee of $235. $5 short of doubling in cost. I've been here since moving across from Ikon and supported IPS in early days financially, paid for lifetime licences which I've begrudgingly accepted would not help IPS survive further down the line. My boss will be on me like a ton of bricks with that increase and with no email support (are you kidding me?) - I am, after 19 years, having to think can we continue. I've always had first rate support from IPS, coupled with a friendly relationship with Matt who's helped me out plenty of times, but I've also let them use my server to test MSSQL drivers and IIS issues when they hosted/worked with the likes of AMD. To turn around to that degree is a proper kick in the nuts. I understand they have to pay the bills, but we all do. A doubling of my licence fee would be a hard one to take on its own but the removal of email support as well? That is not just a small issue.
  14. Why didn't I find that.. oppsie. I'll go sit in the corner.
  15. Having this option for every user is great. My forum members have traditionally preferred to click through to last post. However I used a hack for years to do this but now use the built in settings. However is there the possibility to set a global default - at present it defaults to first post - so that I don't have to explain how to do it to about 10 members every week? 😄
  16. Works ok on 4.6 but on mobile view it would be great if the ignore forum button was below the start topic, as it sort of breaks the responsive width
  17. Still not approved?
  18. Any chance you could put it 4.6 compatible 🙂
  19. It was giving template errors for me. Unforunatley I can't see the logs now as they've cleared out and can't reinstall as tis not flagged as 4.6
  20. This works fine in 4.6 btw
  21. Actually although it was working did notice some errors in the logs - mostly on the template side of things.
  22. Wasn't sure if there would be support for beta so been tinkering myself. It's more fun than the delge of ISO27001 😄
  23. Both 1.1 and 2 Beta's been pretty much flawless. The one strange issue I have is intermittent behaviour of last post/content view. I think it must be the rogue remains of a 4.5 plugin/application somewhere.
  24. FYI it seems to work fine in 4.6
×
×
  • Create New...