Continue Support Ticket 1183825 - Attn: Rupok (if possible)

Hi Superheros,
I have a continuation of Support Ticket 1183825. I suspect it may have to do with .htaccess.
Rupok looked at our initial problem which had to do with a non-Wordpress page not being able to access its images through https. Our latest issue seems to suggest that was symptomatic of issues with our .htaccess file & memory as recently we went to install the update of Jigoshop V1.18.2 before we upgraded to the latest version of Jigoshop as V1 will be no longer supported after Jan 1. This resulted in a 404 error. We are winding back to a previous install.

My question is, can someone upgrade our site with the latest version of Jigoshop, please? The issues to be mindful of include: 1) that the advice from Jigoshop says our Travel Island Theme index page custom changes will not be visible as Jigoshop does not use these anymore (this is perplexing as we have Jigoshop within Travel Island to do the shopping cart functions), 2) its seems as if our ISP (Crazy Domains) or our previous WP Installer, has included a lot of additional referencing code within .htaccess as multiple domain names point to this IP address - this will need to be checked, when the Jigoshop upgrade failed our ISP recommended that we install a php.ini file into the public_html directory and make it recursive (our attempts at this failed). BTW, I did replace the code in .htaccess with the code recommended by Rupok, but it didn't work.

As I am working with a client on this can you let me know if there will be additional costs + an estimate of costs, please?

Kind regards,

  • Nithin

    Hi Richard,

    Hope you are doing good today. :slight_smile:

    Sorry to know that you are having issues with your website, does your entire website ends up in a 404 error? Or is the issue only related to the plugin pages, when you install the Jigoshop plugin? Could you please run a quick plugin/theme conflict test as illustrated in getting support manual (flowchart), and rule out whether any plugin is causing this issue.

    To have a better understanding about this issue, would recommend that you enable debug mode, to check for any related errors about the plugin update. To enable it, open your wp-config.php file located in your root directory, and look for define(‘WP_DEBUG’, false);. Change it to:

    define('WP_DEBUG', true);

    In order to enable the error logging to a file on the server you need to add:

    define( 'WP_DEBUG_LOG', true );
    define( 'WP_DEBUG_DISPLAY', false );

    After making the above changes, please activate the latest version of the plugin. If you still have issues, the related errors will be saved to a debug.log log file inside the /wp-content/ directory.

    Please attach these in your next reply in txt format file, so that we could give a closer look. You can find more details about debugging here.

    As I am working with a client on this can you let me know if there will be additional costs + an estimate of costs, please?

    We don't work for an estimate, you can find more info about support vs custom development here:

    Please do enable support access, so that we could give a closer look at your system too. You can grant access from WPMU DEV > Support > Support Access > Grant Access, or check this manual:

    Please let us know once you enable access, so that we could get this sorted. Have a nice weekend. :slight_smile:

    Kind Regards,

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.