[SEO URL rewrite malfunction in menu only]

  I'll take your word for it.  

[SEO URL rewrite malfunction in menu only]

Another thing I noticed is the skin is still caching.  I FTP'd in with Fetch and deleted all the cache files, including the skin folder's files and the store is back caching them again.  It isn't caching the general files.  Is the skin caching detached from the overall caching feature?

[SEO URL rewrite malfunction in menu only]

9 minutes ago, bsmither said:

I wonder what the category breadcrumb link would have been when viewing a product.

If you searched a product when the nav bar was whacked, it would be fine and the breadcrumb path was correct.  In fact, everything worked fine for both SEO urls and the breadcrumbs other than the nav bar. 

If you used the menu and got the 404 error, I don't think it generated anything.  Not completely sure about that, though.  I can check it next time but I am hoping there isn't going to be a next time.

[SEO URL rewrite malfunction in menu only]

19 minutes ago, bsmither said:

I recommend that one does not use Dreamweaver. (Disclaimer: last time I used it with any seriousness was, like, 20 years ago, and not proficiently, at all. I understand later versions got better, but I still do not trust it to not muck up things.)

I hand code and DW just is convenient for structure, organization and ftp uploading.  It isn't anything like what it was that long ago.  I have used it for decades and it is now quite good and very handy for app development and coding.  I guarantee you the issue isn't with DW.

2 minutes ago, bsmither said:

Sorry, I meant the Sale Items link on the Nav bar.

When the nav bar goes sideways, NOTHING up there works.  Not even the home page icon.  It should simply be the base url of the domain, but this issue even manages to mess that up.

[SEO URL rewrite malfunction in menu only]

16 minutes ago, bsmither said:

even the Sale Items is corrupted

I haven't seen that.  I checked all of the links every time it happened and the ONLY rewrite issue was in the menu.  Featured products, sale items, etc. always worked for me when the menu went sideways.

[SEO URL rewrite malfunction in menu only]

47 minutes ago, bsmither said:

Are you using Dreamweaver?

Yes.

15 minutes ago, bsmither said:

In admin, Store Settings, Advanced tab, set "Enable Caching" to 'Disabled'.

Thanks.  I looked right at that and didn't see it.

20 minutes ago, bsmither said:

I think it has to do with the Smarty plugin 'combine', where it calls CSSMin::minify() using $dirname that (probably) contains the server's root path, as opposed to the domain's httpdocs path.

In the combined CSS file, the set of CSS rules that pertain to the Chosen feature have wrong background:url("path") values. (A clue!)

So would the $glob['rootRel'] and $glob['storeURL'] additions fix this?  It has been working since I added them so far, but every "fix" works temporarily and then it starts again.

[SEO URL rewrite malfunction in menu only]

This popped up again.  I added the two $glob values and cleared the cache and it came back up. 

This issue keeps returning.  We should be able to alias alternate domain names in 301 redirect without it breaking the SEO rewrite or having to do a bunch of code gymnastics.  Who doesn't have alternate domain names to capture alternate spellings or other user mistakes?  That should be assumed in the store code architecture.  I have dozens of other domains with multiple aliases plus SEO rewrites that aren't shopping carts and have never had any issue.

What is really puzzling is that I have had multiple domains aliased to this CC store for YEARS and never had this menu problem.  Did something change in the 6.5.x versions?  Never got it all the way up through 6.4.7.

Also, with all due respect, that caching system is not my favorite.  Is there a way to turn it off?  I'd rather lose speed than deal with the headaches it causes.

Thanks

[Sort menu blank]

That did it.  Thanks as always Brian.  Really appreciate the help.

[Sort menu blank]

Updated to 6.5.6 from 6.5.3 and see just a pair of parentheses on the sort menu.  Re-uploaded all the files and double-checked that the skin (based on Foundation) was also updated.  Tried to attach a screen shot here but the forum server is throwing an error and won't upload it.  Unknown error -200.

[SEO URL rewrite malfunction in menu only]

Thanks Al.  I had moved the domain 301 forwarding of two aliases to the registrar level recently from my Plesk server panel and that may have been the issue.  I pointed them back to my own name servers and re-created the aliases, re-issued the SSL cert to cover everything and it is back working... for now.  Hopefully, that is the problem and this will make a final fix on it.

Appreciate the quick response.

[SEO URL rewrite malfunction in menu only]

A strange issue has started to appear in the menu system of the store.  It hadn't been touched for a while (6.5.3), and suddenly the menu system started throwing these long, convoluted urls that of course resulted in 404 errors.  ALL of the other links on the page work fine with the proper SEO url rewrites.  It is ONLY the menu system.  Even the little home page button on the menu bar throws those bizarre urls, when it should just go to the base domain.  I upgraded to 5.5.6, but that didn't help.

I have tried all kinds of things and each time it has been temporarily "fixed" by a different solution.  Once it was dumping and rebuilding the .htaccess file, another time it was turning off mod_security on my server, another it was changing the SEO settings in the store, clear the cache and set them back and clear the cache again.  Another time it was manually going in and completely dumping the entire contents of the cache folder.  Each of those worked exactly once.  Now, nothing seems to work.

It can be seen at https://anabolnaturals.com  Any ideas would be greatly appreciated.

Here is my .htaccess file:

  

##### START CubeCart .htaccess #####

### GZIP Compression ###
<ifmodule mod_deflate.c>
	AddOutputFilterByType DEFLATE text/text text/html text/plain text/xml text/css application/x-javascript application/javascript
</ifmodule>

### Files Expiration ###
<IfModule mod_expires.c>
    ExpiresActive On
    ExpiresByType text/html "access 0 seconds"
    ExpiresDefault "access 7 days"
</IfModule>

### File Security ###
<FilesMatch "\.(htaccess)$">
  Order Allow,Deny
  Deny from all
</FilesMatch>

### Apache directory listing rules ###
DirectoryIndex index.php index.htm index.html
IndexIgnore *

<ifModule mod_headers.c>
  Header always append X-Frame-Options SAMEORIGIN
</ifModule>

### Rewrite rules for SEO functionality ###
<IfModule mod_rewrite.c>
  RewriteEngine On
  RewriteBase /

  ##### START v4 SEO URL BACKWARD COMPATIBILITY #####
  RewriteCond %{QUERY_STRING} (.*)$
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteRule cat_([0-9]+)(\.[a-z]{3,4})?(.*)$ index.php?_a=category&cat_id=$1&%1 [NC]

  RewriteCond %{QUERY_STRING} (.*)$
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteRule prod_([0-9]+)(\.[a-z]{3,4})?$ index.php?_a=product&product_id=$1&%1 [NC]

  RewriteCond %{QUERY_STRING} (.*)$
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteRule info_([0-9]+)(\.[a-z]{3,4})?$ index.php?_a=document&doc_id=$1&%1 [NC]

  RewriteCond %{QUERY_STRING} (.*)$
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteRule tell_([0-9]+)(\.[a-z]{3,4})?$ index.php?_a=product&product_id=$1&%1 [NC]

  RewriteCond %{QUERY_STRING} (.*)$
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteRule _saleItems(\.[a-z]+)?(\?.*)?$ index.php?_a=saleitems&%1 [NC,L]
  ##### END v4 SEO URL BACKWARD COMPATIBILITY #####

  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteCond %{REQUEST_URI} !=/favicon.ico
  RewriteRule ^(.*)?$ index.php?seo_path=$1 [L,QSA]
</IfModule>

### Default store 404 page ###
ErrorDocument 404 /index.php

## Override default 404 error document for missing page resources ##
<FilesMatch "\.(gif|jpe?g|png|ico|css|js|svg|webp)$">
  ErrorDocument 404 "<html></html>
</FilesMatch>
##### END CubeCart .htaccess #####

 

[Authorize.Net - Accept Hosted]

I don't tweak the look of the payment form very much.  Just a little bit of stuff to make it blend with the store, but I don't mind the basic formatting that gets sent from Authorize.net.  It would be nice to be able to easily blend it so it was visually seamless, but to be honest, I simply don't have the time to do any deep diving into it.  Besides, I think you are probably right that it is part of the formatting coming within the iframe from Authorize.net.

Have you tried using the developer tools in Chrome to look at the live css when the window is open?  If you can identify the classes that are formatting things you want to change inside of the iframe, you might be able to do an override of those classes with your own values using those class names if they load AFTER the payment window.

[Authorize.Net - Accept Hosted]

I believe frameborder html attribute is not valid HTML5 and is obsolete.  If you try validating your css, you will get a message "The frameborder attribute is not supported in HTML5. Use CSS instead."  Try using pure css:  

style="border:none;"

That tells it to remove the border.  Or you can make the border width 0:

style="border:0;"

And also try adding the !important marker if it doesn't work in case there is upstream CSS creating it:

style="border: none !important;"
style="border: 0 !important;"

Don't know if this will work, but it is worth a try!  Good luck.

[Authorize.Net - Accept Hosted]

Back again to this extension.  A new issue has popped up that isn't a problem with the extension per se, but some updates would help to mitigate the issue.  Card testing is a recent problem where a bad actor gets tens of thousands of stolen card numbers and uses the accept hosted window in CC to test them.  Once they get the window open, they can do over 10 submissions per second.  All of them are on a single order with the same order number and amount.  Technically, they are hammering on Authorize.net's site and not the server hosting the CC store.  However, this results in both Authorize.net and the merchant processor shutting down the gateway.  I use AFDS on authorize.net but we really need to try to stop the submissions in the first place.

To help mitigate this, I have modified the hard-coded parameters sent in the Accept Hosted extension gateway.class.php file to this:

 {
				  "settingName": "hostedPaymentPaymentOptions",
				  "settingValue": "{\"cardCodeRequired\": true, \"showCreditCard\": true, \"showBankAccount\": '.$showBankAccount.'}"
				}, {
				  "settingName": "hostedPaymentSecurityOptions",
				  "settingValue": "{\"captcha\": true}"
				}

Requiring the card code and ESPECIALLY showing captcha on the submission form seems to stop them in their tracks.  Unfortunately, I have to go in and redo this mod every time there is a new version of this extension since they are hard coded and not part of the variables stored in the config table.

I think it would be a really helpful mod to this extension to make these selectable in the extension admin, perhaps with a simple checkbox like with a couple of the other parameters there.

Thanks for considering this.

[Upgrading from CentOS to Alma Linux]

I upgraded my server to Alma Linux quite awhile ago and had absolutely no issue with CubeCart or anything else on any of my client's sites.  I doubt you will notice any change at all.  It is basically the same as CentOS, except it is being maintained.  

It reminds me of the switch from mysql to Mariadb back when Oracle took over and decided to be dicks about licensing mysql.  No issues at all with Mariadb either.

[Is CC 6.4.10 compatible on php 8.2?]

26 minutes ago, bsmither said:

Please remind me if there is a conversation about this.

No, it's just one of the things I saw when I tested 6.4.7 with PHP 8.2. so I just mentioned it in case it hadn't been discovered in your testing.

[Is CC 6.4.10 compatible on php 8.2?]

Thanks Brian.  I would guess you already found this issue that was present in CC6.4.7 on PHP 8.2: Customer login technically works but just sits on the login page after submit so the user doesn't think they are logged in.  Probably old news to you.

So many little things that have been made much more strict on PHP 8.2 it is making me crazy doing testing / rewriting on my own systems.  No more loosey-goosey coding and running functions like trim (and others) on foreach loops where there may not be data in some iterations.  Lots of other things too. 

I tell you the #[\AllowDynamicProperties] trick is saving me right now because I can run 8.2 while I rewrite hundreds of class scripts to conform.  I realize how lazy my OO coding has been over the years and am paying for it now.

Tighter requirements make us tighter coders, I guess...

[Is CC 6.4.10 compatible on php 8.2?]

3 hours ago, Janet Parker said:

It's best to consult the official documentation or contact the support team of the eCommerce platform you are using, as they would be able to provide specific information about compatibility with PHP 8.2.

I guess I wasn't too clear.  I develop and host data management systems primarily but also have a few clients who are doing eCommerce using CubeCart on my server.  I am finishing up re-coding and testing my systems with php 8.2 and will be switching the last data systems domains to 8.2 shortly.  All of my other clients are moved to php 8.2 already.  My CubeCart sites will be the only 8.1 users on my server.  I would like to move them to 8.2 so I can remove all other php versions.

3 hours ago, Janet Parker said:

However, according to the official release notes of CubeCart 6.4.10, there is no mention of compatibility with PHP 8.2. Therefore, it's possible that CubeCart 6.4.10 may not be fully compatible with PHP 8.2, and some issues may still occur.

Yes, that is why I posted in the CubeCart forum to see if someone like Brian had any additional info.  It would be nice if php version compatibility was part of the documentation of each CC version update.

3 hours ago, Janet Parker said:

It's recommended to test the upgrade on a staging or development environment before performing the upgrade on a production site. Additionally, it's always best to ensure that your site and its components are fully compatible before making any upgrades to avoid any issues or downtime. 

I tested 6.4.7 and know that doesn't work so before I go to the trouble of doing a bunch of testing on 6.4.10, I wanted to post here to see if anyone like Brian knew if it would work or not.  Mostly if they already knew it wouldn't work so I wouldn't waste a bunch of time testing something that was already known to not work.

[Is CC 6.4.10 compatible on php 8.2?]

I have been updating my own data systems to be compatible with php 8.2 and also moving my clients sites that aren't using CC (non-eCommerce clients) to 8.2.

I have my CC stores at 6.4.7 and tested one with php 8.2 and it had some significant issues that made it a no-go.  I will be updating stores to 6.4.10 shortly and wanted to know if this latest version is php 8.2 compatible.

[CC and php 8.1]

1 hour ago, bsmither said:

I would NOT apply the diff file to the filediff program. Guaranteed to result in a hot mess.

 

 

No no.  I have notes of what files have been changed in the skin.  I will run DiffMerge on each of them and carefully update the code on the new CC version skin.  I have very clear remarks on every change.  I just need to carefully examine the code between the old and new to make sure I understand any changes in the new that may affect my modifications.  It is slow and tedious.  And, as I said, I have to think.  Hate that.

[CC and php 8.1]

Thanks Brian.  I have a filediff program.  I was just wondering if I needed to go through it file by file.  Just lazy but since things are pretty significantly re-arranged on my Foundation skin variant, I have to sit and transpose the differences instead of viewing the difference pages and approving the automatic code block updates left to right in the file diff edit window.

I hate it when I have to actually do some work.  Even worse when that work requires me to think.  Thinking is hard.

[CC and php 8.1]

Just wanted to pop back in and thank Brian and Al (and whomever else worked on the update) for the php 8.1 compatibility.  Finally got a rare minute to jump over and do some store upgrades and then switch them to php 8.1.

As always, your work is very much appreciated.

One question - Do you know if anything changed in the Foundation skin between 6.4.4 and 6.4.7?  I have a skin that is based on Foundation but is significantly altered in its element arrangement so I would like to not rebuild it if there is no reason to.

Thanks

 

[CC and php 8.1]

My guess: Boooooom!  

Really, you don't have to go through all that.  I don't want to hack CC just because I am a type A PITA.  I can wait for everything to catch up in a future release... I swear I can...  Really... ahhhhhhhhhhhh!

[CC and php 8.1]

That would be very generous of you to do.  PHP 8 has only been out since the very end of November 2020, so that's just under 18 months.  Lots of changes and depreciated / removed functions and conventions so it will understandably take a while for everyone to clean their code.   

All my stuff works fine on 7.4 too, I just am a bit impatient to work with some of the 8.1 improvements.  I have it installed in my MAMP Pro testing server and develop only with that to future-proof as far out as possible so it is important that I have it on my production server, which I do for the domains I use.

For CC, I can just leave it on 7.4 until all is ready and then I will clean 7.4 off the server.

As always, thanks for your help and response Brian.  It is greatly appreciated.

[CC and php 8.1]

Thanks Brian. 

Do you know if Smarty 4 in CC645?  Obviously, if a single third-party component isn't compatible, then the whole thing isn't.

I run PHP as a PFM Application per domain so I will keep 7.4 for the CC clients and wait for the plugins to catch up if they haven't yet.

It would be great if Al specifically announces when the CC version is released that is tested compatible with PHP 8.1.  (wink, wink, nudge, nudge)..