bsmither

Please look in CubeCart's System Error Log for any entries that might pertain to the sending of emails. You may have set CubeCart to use the mail() function in admin, Store Settings, Advanced tab. "Could not instantiate mail function." comes from the PHPMailer library, when it wants to use whatever email service that PHP is told is available on the server - Exim, Sendmail, Qmail, whatever - but that this service has reported it cannot be used. This may be because the amount of emails has hit a limit according to the settings of that email service: quantity per batch, quantity per hour, quantity per day, whatever. CubeCart (from what I can tell) will send a batch of 20 emails pausing 2000 milliseconds between each batch until done (or until something goes wrong.) Please consult with your hosting provider to determine if there are email sending limits being enforced. I do not know of a way to restrict the second sending of a newsletter to only those who it was not successfully sent to.

Yet, it is just a matter of copying the folder from the CC651 package.

No, nothing new here. Again, one of the errors in the above post suggests that you do not have a complete /classes/PHPMailer/ folder.

Again, make sure that the three middle lines all start at column one - no leading spaces.

Ok, nothing wrong in that line. However... In the file class.gui.head_js.php, lines 15-19, there is this: if($module_config['applepay']=='1') { $head_js[] = <<<EOT <script src="https://applepay.cdn-apple.com/jsapi/v1/apple-pay-sdk.js"></script> EOT; } The <<<EOT is called 'Heredoc' text syntax. There are rules for how Heredoc is written: Since you are running PHP 7.2, these lines 15-19 must be written as follows: if($module_config['applepay']=='1') { $head_js[] = <<<EOT <script src="https://applepay.cdn-apple.com/jsapi/v1/apple-pay-sdk.js"></script> EOT; } So, determine if your text viewer is also an editor and if so, make the changes to the above code.

If your site is hosted, your hosting provider should provide a way for you to manage your site - many times with Cpanel. Cpanel has a file viewer tool. Use it to find and view the file /modules/plugins/paypal_commerce/hooks/class.gui.head_js.php. The viewer should show line numbers, so copy the statement at line 20 and paste it in your reply to this forum conversation.

Please let us know the version of the PayPal Commerce plugin. That can be determined by using a text viewer to look at the plugin file config.xml. There will be a statement near line 20 that reads something like: <version>1.8.5</version> Then, look at the plugin file /hooks/class.gui.head_js.php, and let us know what line 20 looks like. Also, let us know the exact version of PHP that is running your site.

Something is throwing an "exception", and maybe CC651 is not getting it logged into the database. Please make this edit in /classes/debug.class.php: Near line 500, find: public function exceptionHandler($e) { $message = "[<strong>Exception</strong>] \t".$e->getFile().":".$e->getLine()." - ".$e->getMessage(); $this->_errors[] = $message; $this->_writeErrorLog($message, 'Exception'); } Change to: public function exceptionHandler($e) { $message = "[<strong>Exception</strong>] \t".$e->getFile().":".$e->getLine()." - ".$e->getMessage(); trigger_error($message,E_USER_ERROR); // $this->_errors[] = $message; // $this->_writeErrorLog($message, 'Exception'); } Near line 480, find: $this->_errors[] = $error; Change to: $error = (stristr($error_string, "[<strong>Exception</strong>]")) ?: $error; $this->_errors[] = $error; When you get the blank screen, maybe now there will be the reason for it in the System Error Log. Also, one of the errors in the above post suggests that you do not have a complete /classes/PHPMailer/ folder. Also, please consider using PHP 8.1 when running CC651.

You said, "When I tried the second fix I noticed that the line numbers were different, however I still applied the fixes." Note that the second mentioned issue in the Github (#2566) had already been applied in CC640. Your screen grab above shows you are running CC651 - so that edit was not applicable. If those "fixes" you made are still in this installation, at the wrong line numbers, you will need to remove them.

The 'errorlog order display" file shows only that a code snippet caused PHP to complain about a "token" that probably was not provided, which somehow triggered a need to log in to admin. Please remind us the exact version of PHP and CubeCart this installation is running (regardless that your "tag line" says CC614).

Could you please read these issues in the Github and determine if anything might apply? Bad tax calculation with absolute option price and tax inc https://github.com/cubecart/v6/issues/3301 Applied to CC652 (not yet released) Product Options - Bugs with mixture of absolute / non absolute option value https://github.com/cubecart/v6/issues/2566 Applied to CC640-b1

In admin, Store Settings, Advanced tab, enable Debug Mode and enter your local IP address in the next field (www.showmyip.com). When fetching pages, the browser will want to show a popup window. Allow it to do so. This window will show certain debug info, including the cookie that CubeCart used to verify the logged-in state of the user. (On page loads, except for Firefox, new debug data is appended to the end of the current debug data in the popup.) Compare the debug info between a successful login on Chrome versus an apparent failed login on Edge.

Please try logging out (no guarantees). http://www.mystore.com/admin.php?_g=logout using the appropriate name for your store and using the appropriate name for the admin script. This might clear out some cookies. Otherwise, try deleting cookies for your domain, or try a different browser/computer, or try a "private" browser tab (gets fresh cookies).

The simplest way to make this edit is to swap the position of the {/if} statement and the <div class=row> statement that is just above it.

This is a known bug starting with CC6410, and will be fixed in CC652. See: https://github.com/cubecart/v6/issues/3316 In the Foundation skin template content.certificates.php, lines 15-20: From: {if !empty($GC.image)} <div class="row"> <div class="small-12"><img src="{$GC.image}" alt="{if isset($GC.image_tags.alt)}{$GC.image_tags.alt}{else}{$LANG.catalogue.gift_certificates}{/if}"{if isset($GC.image_tags.title)} title="{$GC.image_tags.title}"{/if} /></div> </div> <div class="row"><div class="small-12 large-8 columns"><label for="gc-value">{$LANG.common.value} ({$CONFIG.default_currency})</label><input type="text" name="gc[value]" id="gc-value" value="{$POST.value}" placeholder="{$LANG.common.value} {$LANG.form.required}" required></div></div> {/if} To: {if !empty($GC.image)} <div class="row"> <div class="small-12"><img src="{$GC.image}" alt="{if isset($GC.image_tags.alt)}{$GC.image_tags.alt}{else}{$LANG.catalogue.gift_certificates}{/if}"{if isset($GC.image_tags.title)} title="{$GC.image_tags.title}"{/if} /></div> </div> {/if} <div class="row"><div class="small-12 large-8 columns"><label for="gc-value">{$LANG.common.value} ({$CONFIG.default_currency})</label><input type="text" name="gc[value]" id="gc-value" value="{$POST.value}" placeholder="{$LANG.common.value} {$LANG.form.required}" required></div></div>

Please, let us have a web address where we can view your GiftCard page.

Starting the CubeCart "Setup" process (which really only means to create or update the database), there is a "Drop Table" checkbox, and the colorful full-width clickable panels that show a first-time installation, or an update. It seems you did not have the Drop Tables checkbox checked - otherwise all tables would be empty. But then, you probably selected Full Install - maybe the only choice. The Full Install will "truncate" (remove all rows) the CubeCart_category, CubeCart_inventory, and CubeCart_category_index database tables, and load them with initial sample data. No other action is taken against the other existing database tables - if they exist. The Setup process checks for the existence of the /includes/global.inc.php file, and only if present (that file won't be present on an FTP upload or unzipped archive onto a fresh, cleaned folder of all other CubeCart code), and only if having key data points in it, will Setup offer an Upgrade choice. So, from the database backup, the only tables you need to restore are those three that were truncated.

Deleted the 'config' row in the database, fetched the Store Settings page, but code is still present in the Offline Message editor? Please find the web server's error log (not PHP's error log). If the web server is logging "Denied by Policy Rule" or some such (there might not be any logging at all with respect to this), then I would think the hosting provider has integrated some sort of security module on the web server. There are numerous forum conversations that conclude these protocols interfere with common data being saved when passing through the web server.

Ok, this is interesting. It says this is PHP 7.3. That means CC65+ will have myriad problems. CC6410 should show several odd behaviors, but shouldn't crash when showing the install/setup screen.

Create a file named info.php. The contents of that file are: <?php phpinfo(); ?> Have your browser ask for this file specifically: http://www.olivewoodturning.co.uk/info.php (This file already exists at /setup/info.php.) If you still get a 500 error, the problem is not with CubeCart.

So those errors were generated from CC649. Is there an "error_log" file where CC651 is being installed? Also, those "Illegal String Offset" errors imply that there is being a search made against store inventory where the data passed in to that search function is a plain word, as opposed to an array having a word or words. A bug report has been made.

Would these errors be from an earlier version? Line 1782 is a comment line in catalogue.class.php, version 6.5.1.

PHP 8.1 is a good version to run CC651, so I would have to think the problem lies elsewhere. My search on the Internet for these errors all mention the programming language C++. There could be a separate error log file belonging to PHP. If there might be a separate error log file that PHP will write to, see the following conversation that could help get access to that error reporting: https://forums.cubecart.com/topic/51550-how-to-create-the-error-log/ If that gives no additional info, I encourage you to contact your hosting provider.

I have never seen this before. Please let us know what version of PHP is being used.

This issue was fixed in CubeCart 6.2.7 a few years ago. Please see: https://github.com/cubecart/v6/commit/b54b241d2445d927c24682feb35aa7375e01c1a7