Jump to content

Featured Replies

Posted

Hello,

we have strange problem (I don't see any JS errors in the console so it's hard to debug it by my own) with the guest replies.

When I go to topic and try add a reply as a guest - all is fine. But then the small circle is pending and the editor isn't showing up.

Of course done:

- disabled all plugins/apps and tested, without success.

Any advice would be helpfull.

 

What I'm speaking about:

 

 

Unfortunately, before we can proceed with support, it looks like you are hiding our copyright/branding line "Powered by Invision Community" but did not purchase the copyright/branding removal license. By the license agreement, this is required to stay 100% visible on all pages or you will need to purchase the removal license. Please restore this to all pages and ensure nothing is covering it and it is 100% legible or purchase the removal license from the Client Area.

  • Author

Sorry, it wasn't intentional. We have important advert there. I've added margin-bottom and now it's visible? It's fine or adjust it a little?

 

 
 

Please confirm a location you are allowing posting

I can see the issue happening. Before I look any further, could I confirm that once everything was disabled, you also cleared cache before you tested again? I ask as with it being a guest page, it will be subject to guest cache

  • Author
24 minutes ago, Marc Stridgen said:

could I confirm that once everything was disabled, you also cleared cache before you tested again?

Correct sir.

Please disable cloudflare in the first instance. Its very likely this is what I causing issues here

  • Author

Disabled. Didn't helped much, issue persists.

Edited by topek

I have created a ticket for you on this. Someone will be in contact as soon as possible

  • 4 weeks later...
  • Author

Hello,

when it will be applied in any future release? 🙂

I've got reply, that it's confirmed and will be fixed.

19 minutes ago, topek said:

Hello,

when it will be applied in any future release? 🙂

I've got reply, that it's confirmed and will be fixed.

Looking at present it does look like it will be applied to 4.7.3

Recently Browsing 0

  • No registered users viewing this page.