Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author alekv

    (@alekv)

    This is very strange. There are also two tabs missing. This points to a problem with the JavaScript scripts.

    Are you using some sort of ad or script blocker? If yes, could you turn it off, or use a different browser?

    Could you also take a look at the browser dev console. It usually shows if there are scripts that are being blocked.

    Thread Starter beiert

    (@beiert)

    Ok, i tried it with firefox too, same problem.
    The dev console says “500 internal server error”

    I checked the server log files too. Here are the screenshots:

    https://www.dropbox.com/sh/e3k1n90rrsgy27e/AADg9rfx155GEvcUg6lCHQ3ra?dl=0

    I used your plugin before without problems, the problem came after upgrading to the trial premium version.

    Plugin Author alekv

    (@alekv)

    Ok. I see where the problem is.

    I added a new check in the recent version to detect if the purchase confirmation page is being redirected to a custom page. That is the case on your install.

    Some custom pages don’t work properly with WooCommerce, so we need a way to debug this.

    But the check for the redirect receives an array instead of a string on your install. I’m not sure why, because the field it is checking is usually a string.

    I will build in safeguard and release the fix tomorrow morning.

    If you allow me to get access to your install I could even test the fix and find out why there is an array being returned instead of a string. In case you agree, please send me the access (FTP and WP admin) to [email protected]

    Plugin Author alekv

    (@alekv)

    Just found out why there can be an array. If multiple redirects happen on the regular purchase confirmation page, then the function receives an array of all redirects. I’ll build in some logic which will handle this properly and publish it tomorrow.

    Thread Starter beiert

    (@beiert)

    ok, i will write an email with the login credentials in the next minutes.

    Thank you

    Plugin Author alekv

    (@alekv)

    Just in case you wonder. You can keep the plugin running in the mean time, as the error only happens when you try to access the back-end settings page.

    Plugin Author alekv

    (@alekv)

    Hi Thilo

    That’s been fixed in version 1.10.1 which I just published.

    Let me know if you need anything else.

    Regards
    Aleksandar

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘“Save button” is gone’ is closed to new replies.