KirkM

I'll take your word for it.

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?

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.

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. 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.

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.

Yes. Thanks. I looked right at that and didn't see it. 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.

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

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

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.

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.

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 #####

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.

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.

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.

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.