fullworks

Having studied your site I have some theories

1. W3 Total Cache is cached this error page
2. A plugin orntheme javascript is making the form submit twice

In the first instance can you try turning W3 total Cache off temporarily and see if the issue resolves. If not please try deactivating all plugins and test again.

Let me know if you find anything relevant.

Good idea. I’ll look into that.

Hi,

I have just been testing on system and it is working fine. But I can see on your it is not.

The API code is correct or you would get ‘invalid API code’

The message you are getting is when the api returns ‘sent_recently’ :

Why it is doing this – for your slack team – I don’t know?

I wish I could recreate it as I could then try and debug your situation.

As it suddenly appeared after working,perhaps there is a setting on Slack – let me know your thoughts.

Did you get a solution to this, I have the same issue.

Thanks

also I think line 330 should be
static function register()

Yes, the generally published htaccess doesn’t take into consideration any queries when you are logged in, so when inside admin certain actions like sorting post by author will fail.

Also the .htaccess solution doesn’t deal with POST queries,which is a technique employed by some hacking tools.

Thanks for identifying this.

This can be fixed by urldecode, or indeed if I get the chance to test it – changing over to ‘REQUEST’ matching

Thanks, I will investigate further and share with you any discovery.

Currently the parameter to the shortcode do not work. The parameters are only really title / before text & after text. The functionality does work though with [join-slack]

The widget does work fully.

As mentioned I will fix that in the next release. However I haven’t had any time to focus on this at the moment.

Same issue here on 4.4

Seemed that just editing teh page and re-saving re-activated the shortcode. Very strange.

Its seems the parameters are not being passed correctly. I’ll fix that in the next release.

Sorry in the delay in getting back to you. I’ll give you some examples.

Are you still getting this with the current version?

Many thanks for you positive comment. I’m glad that it is helping people.

I was able to recreate the issue and have applied your fix, and it seems good in testing.

Thanks