it is really not work well in wordpress4.9.5

After upgrade to wordpress4.9.5, it really not work well, it caused frontend like mass and it seems still work even it is after activated, I am not sure the reason.

if I type and input text content in text editor area, there will errors show up:https://prntscr.com/jarhr6

The plugin is working fine in our dev environment (with WP 4.9.5) with default theme Twenty Sixteen and plugins
https://dev.nanodesignsbd.com/submit-ticket/

or it does not work well with Redis cache?

If it is deactivated, and then press activate, it can not be activated even there is a message show activated, please check the screenshot:https://prntscr.com/jardaw

We do not have any Redis cache enabled server yet. What about clearing the Redis server cache when the plugin activated?

You can plug your action anytime using the action hook provided by the plugin:
nanosupport_installed

Here’s the source:
https://github.com/nanodesigns/nanosupport/blob/master/includes/ns-install.php#L129

Hello @wzislam,

Thanks for your reply.

The plugin is working fine in our dev environment (with WP 4.9.5) with default theme Twenty Sixteen and plugins
https://dev.nanodesignsbd.com/submit-ticket/

I checked your official site, and the same issue when input text in title, please check the screenshot:
https://prntscr.com/jb7v69

Also, the same issue with response fields:
https://prntscr.com/jb80vv

I can make it work, and I just support it conflict with a plugin of session control.

Alex

Alex

Yes, now we can replicate the issue too. But despite the error in red in console the Editor, Ticket Subject, and Response fields are doing their job.

BTW we should fix this, and inshALLAH with the next release we will adopt the latest release of this repository to mitigate with the issue.

You can follow up the issue here:
https://github.com/nanodesigns/nanosupport/issues/55

Thanks.

Sorry for my poor english, yet it works well, and doing their job.

When I said “really not work well”, I mean I am sure there is small issue:)

and thanks again.

5 star support.

Alex

The issue is resolved and is ready to release with v0.5.0

Closing here.