• Installed first version and is crashed my site. Traditional login failed and only secondary login can gain access to site now. Pages to not display in customizer feature anymore and view page function removes user from wordpress completely. It is a mess and I gave the details to the developer and they refused to help restore my site and deny any responsibility (of course). This is a totally new plugin with very little live versions running. Beware.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Mayeenul Islam

    (@wzislam)

    @michael DeVore
    Sorry to hear that but we actually did not find any connection to that occurrence with our plugin. ??

    You said:

    Traditional login failed and only secondary login can gain access to site now. Pages to not display in customizer feature anymore

    FYKI, NanoSupport NEVER USED any admin panel tweaks that can interfere with:
    – Customizer, or
    – Default Login behavior

    You said your /wp-admin is not working, but /wp-login.php is working, we’re afraid, NanoSupport didn’t tweaked any login feature like /wp-admin, so it has nothing to harm you on that feature!

    You said it harmed your Customizer, but as said the plugin never touched any Customizer feature, so it’s totally a balant claim with no evidence. Here’s an animated screencast showing customizer is perfectly working with our plugin:
    https://gph.is/29ZO8cW

    You demanded:

    …view page function removes user from wordpress completely.

    It’s ridiculous ??, we found no declaration of wp_delete_user() in any of our 51 files of NanoSupport.

    We can prove what we are saying, you can check the code, it’s open source: https://github.com/nanodesigns/nanosupport (current version 0.1.1)

    We’ve tested with our plugin completely uninstalled, and the same thing was happening to your site, so it’s clear that, the plugin did not harm your site.

    After all the long testing sessions we’re claiming that:

    ????????????????????????????

    ?? We found no connection of the occurances you are demanding without any evidence with NanoSupport, and the code everywhere in NanoSupport is neither responsible for any mess to Customizer or Default login mechanism. We’ve several servers and we’ve tested things out in our QC sessions several times. So, we can assure you that, things happened to your site cannot be happened by NanoSupport by any means. We found no trace. We’ve tested with all our aspects, and cross-checked things with our dev and testing environments (We’ve sent you all the details).

    We’re firmed with our findings that, NanoSupport never did that. We found no trace or link of wrong doing with NanoSupport.

    ????????????????????????????

    You said,

    …I gave the details to the developer and they refused to help restore my site and deny any responsibility (of course).

    As we’ve already proved that, what happened was never happened due to our plugin, so how come we take any responsibility of your wrong turn?

    We can easily conclude that, what happened, was happened either due to your faulty theme or any other plugin. As NanoSupport was deactivated, deleted how come it’s causing something as you reported!!!

    Please debug your site as directed here:
    ?? https://wordpress.stackexchange.com/tags/debug/info

    Hope, you will soon find out your buggy particle and embrace NanoSupport as a companion to your site.
    Thank you

    Thread Starter mdevore342

    (@mdevore342)

    This is simple deduction. Your site is working perfect then you install a plugin that has many known bugs and new to the marketplace and all the sudden the site isn’t functioning correctly immediately after install or your plugin. It doesn’t take a rocket scientist to figure out what the problem is. By your own admission when we first tried the plugin your comments where that this was a new product and still working out all the bugs. Don’t admit to having a untested product with bugs and turn around and tell the world hey it works on our computer and our website so it must work perfect everywhere else, that is a microsoft fallacy. Sham Sham on you.

    Plugin Author Mayeenul Islam

    (@wzislam)

    Thank you for your deduction.
    Let’s the world decide.

    I believe we should note one thing here, Plugin conflict and bugs are something that is not uncommon.

    As for me, I got no problem with this plugin, even in multisite install.

    Plugin Author Mayeenul Islam

    (@wzislam)

    Thank you @ganisirawan

    Thanks for testing in Multisite. Though currently we’re not announcing the plugin for multisite, but we will inshALLAH announce it after more decentralized testing.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Crash and burned’ is closed to new replies.