Rhapsody

The following are captured in the error log so they may be investigated for future updates: Two Smarty errors: PHP Deprecated: Using php-function "stripos" as a modifier is deprecated and will be removed in a future release. Use Smarty::registerPlugin to explicitly register a custom modifier. in .../shop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_compile_private_modifier.php on line 112 PHP Deprecated: Using php-function "strstr" as a modifier is deprecated and will be removed in a future release. Use Smarty::registerPlugin to explicitly register a custom modifier. in .../shop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_compile_private_modifier.php on line 112 TCPDF errors: PHP Warning: Undefined array key "thead" in .../shop/vendor/tecnickcom/tcpdf/tcpdf.php on line 16679 PHP Warning: Undefined array key "trids" in .../shop/vendor/tecnickcom/tcpdf/tcpdf.php on line 19746 PHP Warning: foreach() argument must be of type array|object, null given in .../shop/vendor/tecnickcom/tcpdf/tcpdf.php on line 19746 PHP Warning: Undefined array key "trids" in .../shop/vendor/tecnickcom/tcpdf/tcpdf.php on line 19778 PHP Warning: foreach() argument must be of type array|object, null given in .../shop/vendor/tecnickcom/tcpdf/tcpdf.php on line 19778

Make sure that the necessary PHP installed modules (not the TB modules) are activated on your cPanel. One easy check is to open two tabs of the cPanel PHP version selector. Use the older version of PHP in one tab, and the newer version of PHP in the other tab. Then go through and make sure the same modules are activated in the newer version as the older version. This approach definitely helped resolve 500 errors when I transitioned to newer versions of PHP.

I'm getting used to it but am generally resistant to change - just a stubborn old guy.... I have customized to BO templates for Customers, Addresses, Carts - do I need to verify that these are not impacted? The Icons in the top menu bar should have mouse over titles added to make them easier to identify the functions they perform, similar to those on the right side of the top bar.

Thank you! I have grown cynical with many pop up boxes that appear in applications and typically don't read them. It was a new behavior exhibited in Thirty Bees that I was not expecting. I do appreciate the support.

I just did a Bleeding Edge update on 28 Oct 2024 and note there is now a "Need Help ..., Premium Modules ...., Love Thirty Bees ...." message in the top bar and bottom right of the BO screen. These are annoying! Additionally clicking the "x" to close them pops up another window "ThirtyBees - Empowering your business to reach new heights!", rather than closing the item. Can this be fixed to close them properly, and a way to disable them altogether be provided?

I was looking on how to mark some topics I posted as solved. I assume there is a time limit that prevents editing the original post title to annotate it as solved as I am unable to. Is there a forum FAQ or instructions how to mark a topic as solved?

Thanks! That did it. I commented out 'onclick' in the isCleanHtml function override file which results in a successful product save.

I am receiving errors when saving product descriptions and short product descriptions that contain links that have the javascript onclick function per below. This code results in the errors ×2 errors The description field (English (English)) is invalid. The description_short field (English (English)) is invalid. <a title="Subdomain Availability Check" dir="ltr" onclick="window.open('https://crew-mgr.com/website-check/','Subdomain Check','width=600,height=750,left=500,top=50');return false;" href="https://crew-mgr.com/shop/home/1-new-website-with-2-month-subscription.html" target="_self"><span style="color: #3d00ff;">Check Subdomain Availability</span></a> I know that when editing the product and saving it, there is a validation that takes place, and the onclick is probably causing the validation to fail. What I don't know is which files are used to conduct the validation. I have worked around this by manually saving the raw html in the database with phpMyAdmin. Can anyone provide assistance on which file is used to conduct the validation for saving a product so I can override it to validate the code with the onclick?

@wakabayashi - similar to 30knees I am seeing the same error log entries. It appears to be generated both when logging in and logging out. I have toggled all the configuration settings and saved them to see if that helps. It still creates the error log. Any ideas?

I am so embarrassed! I had overrides created on a much older version of ThirtyBees across all three shops. Once I updated the overrides using the newer core code, the problem was fixed. My apologies for wasting your time. Thanks for all the troubleshooting assistance!

Another data point. I have 3 shops hosted on different Linux hosts. One is on GoDaddy, and the other two on Glowhost. All three shops exhibit the same behavior when upgraded to bleeding edge. Rolling back to stable 1.5.1 restores the images.

Mod rewrite is on and functioning. What I can't figure out is when I manually edit the .htaccess file (using cpanel rather than the TB save function) I still can't get the proper product image link redirection. I've also used an incognito window to make sure the browser isn't caching anything when I try this. Feel free to pass on any other troubleshooting tips.

Making progress - I found that turning off friendly URLs fixes the images on bleeding edge. I'll be looking into why the friendly path get broken. Pass on any ideas you may have.

I'm on a shared hosting account on Apache. This is one of two shops I've tried bleeding edge on that breaks the product images. before and after update to bleeding edge pasted below. .htaccess excerpt TB version 1.5.1 # Domain: chnyc.us RewriteRule . - [E=REWRITEBASE:/shop/] # Webservice API RewriteRule ^api$ api/ [L] RewriteRule ^api/(.*)$ %{ENV:REWRITEBASE}webservice/dispatcher.php?url=$1 [QSA,L] # Images RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^([0-9])(\-[_a-zA-Z0-9\s-]*)?(-[0-9]+)?/.+?([2-4]x)?\.jpg$ %{ENV:REWRITEBASE}img/p/$1/$1$2$3$4.jpg [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^([0-9])(\-[_a-zA-Z0-9\s-]*)?(-[0-9]+)?/.+?([2-4]x)?\.webp$ %{ENV:REWRITEBASE}img/p/$1/$1$2$3$4.webp [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?(-[0-9]+)?/.+?([2-4]x)?\.jpg$ %{ENV:REWRITEBASE}img/p/$1/$2/$1$2$3$4$5.jpg [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?(-[0-9]+)?/.+?([2-4]x)?\.webp$ %{ENV:REWRITEBASE}img/p/$1/$2/$1$2$3$4$5.webp [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?(-[0-9]+)?/.+?([2-4]x)?\.jpg$ %{ENV:REWRITEBASE}img/p/$1/$2/$3/$1$2$3$4$5$6.jpg [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?(-[0-9]+)?/.+?([2-4]x)?\.webp$ %{ENV:REWRITEBASE}img/p/$1/$2/$3/$1$2$3$4$5$6.webp [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?(-[0-9]+)?/.+?([2-4]x)?\.jpg$ %{ENV:REWRITEBASE}img/p/$1/$2/$3/$4/$1$2$3$4$5$6$7.jpg [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?(-[0-9]+)?/.+?([2-4]x)?\.webp$ %{ENV:REWRITEBASE}img/p/$1/$2/$3/$4/$1$2$3$4$5$6$7.webp [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?(-[0-9]+)?/.+?([2-4]x)?\.jpg$ %{ENV:REWRITEBASE}img/p/$1/$2/$3/$4/$5/$1$2$3$4$5$6$7$8.jpg [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?(-[0-9]+)?/.+?([2-4]x)?\.webp$ %{ENV:REWRITEBASE}img/p/$1/$2/$3/$4/$5/$1$2$3$4$5$6$7$8.webp [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?(-[0-9]+)?/.+?([2-4]x)?\.jpg$ %{ENV:REWRITEBASE}img/p/$1/$2/$3/$4/$5/$6/$1$2$3$4$5$6$7$8$9.jpg [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?(-[0-9]+)?/.+?([2-4]x)?\.webp$ %{ENV:REWRITEBASE}img/p/$1/$2/$3/$4/$5/$6/$1$2$3$4$5$6$7$8$9.webp [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?(-[0-9]+)?/.+?([2-4]x)?\.jpg$ %{ENV:REWRITEBASE}img/p/$1/$2/$3/$4/$5/$6/$7/$1$2$3$4$5$6$7$8$9$10.jpg [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?(-[0-9]+)?/.+?([2-4]x)?\.webp$ %{ENV:REWRITEBASE}img/p/$1/$2/$3/$4/$5/$6/$7/$1$2$3$4$5$6$7$8$9$10.webp [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?(-[0-9]+)?/.+?([2-4]x)?\.jpg$ %{ENV:REWRITEBASE}img/p/$1/$2/$3/$4/$5/$6/$7/$8/$1$2$3$4$5$6$7$8$9$10$11.jpg [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?(-[0-9]+)?/.+?([2-4]x)?\.webp$ %{ENV:REWRITEBASE}img/p/$1/$2/$3/$4/$5/$6/$7/$8/$1$2$3$4$5$6$7$8$9$10$11.webp [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^c/([0-9]+)(\-[\.*_a-zA-Z0-9\s-]*)(-[0-9]+)?/.+?([2-4]x)?\.jpg$ %{ENV:REWRITEBASE}img/c/$1$2$3$4.jpg [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^c/([0-9]+)(\-[\.*_a-zA-Z0-9\s-]*)(-[0-9]+)?/.+?([2-4]x)?\.webp$ %{ENV:REWRITEBASE}img/c/$1$2$3$4.webp [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^c/([a-zA-Z\s_-]+)(-[0-9]+)?/.+?([2-4]x)?\.jpg$ %{ENV:REWRITEBASE}img/c/$1$2$3.jpg [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^c/([a-zA-Z\s_-]+)(-[0-9]+)?/.+?([2-4]x)?\.webp$ %{ENV:REWRITEBASE}img/c/$1$2$3.webp [L] .htaccess excerpt TB Bleeding Edge # Domain: chnyc.us RewriteRule . - [E=REWRITEBASE:/shop/] # Webservice API RewriteRule ^api$ api/ [L] RewriteRule ^api/(.*)$ %{ENV:REWRITEBASE}webservice/dispatcher.php?url=$1 [QSA,L] # Images # categories images RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^categories/([0-9]+)(\-[_a-zA-Z0-9\s-]*)?/.+?([2-4]x)?\.(gif|jpeg|jpg|png|webp)$ %{ENV:REWRITEBASE}img/c/$1$2$3.$4 [L] # categoriesthumb images RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^categoriesthumb/([0-9]+)(\-[_a-zA-Z0-9\s-]*)?/.+?([2-4]x)?\.(gif|jpeg|jpg|png|webp)$ %{ENV:REWRITEBASE}img/c/thumb/$1$2$3.$4 [L] # manufacturers images RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^manufacturers/([0-9]+)(\-[_a-zA-Z0-9\s-]*)?/.+?([2-4]x)?\.(gif|jpeg|jpg|png|webp)$ %{ENV:REWRITEBASE}img/m/$1$2$3.$4 [L] # products images RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^products/([0-9])(\-[_a-zA-Z0-9\s-]*)?/.+?([2-4]x)?\.(gif|jpeg|jpg|png|webp)$ %{ENV:REWRITEBASE}/$1/$1$2$3.$4 [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^products/([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?/.+?([2-4]x)?\.(gif|jpeg|jpg|png|webp)$ %{ENV:REWRITEBASE}/$1/$2/$1$2$3$4.$5 [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^products/([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?/.+?([2-4]x)?\.(gif|jpeg|jpg|png|webp)$ %{ENV:REWRITEBASE}/$1/$2/$3/$1$2$3$4$5.$6 [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^products/([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?/.+?([2-4]x)?\.(gif|jpeg|jpg|png|webp)$ %{ENV:REWRITEBASE}/$1/$2/$3/$4/$1$2$3$4$5$6.$7 [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^products/([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?/.+?([2-4]x)?\.(gif|jpeg|jpg|png|webp)$ %{ENV:REWRITEBASE}/$1/$2/$3/$4/$5/$1$2$3$4$5$6$7.$8 [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^products/([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?/.+?([2-4]x)?\.(gif|jpeg|jpg|png|webp)$ %{ENV:REWRITEBASE}/$1/$2/$3/$4/$5/$6/$1$2$3$4$5$6$7$8.$9 [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^products/([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?/.+?([2-4]x)?\.(gif|jpeg|jpg|png|webp)$ %{ENV:REWRITEBASE}/$1/$2/$3/$4/$5/$6/$7/$1$2$3$4$5$6$7$8$9.$10 [L] RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^products/([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9\s-]*)?/.+?([2-4]x)?\.(gif|jpeg|jpg|png|webp)$ %{ENV:REWRITEBASE}/$1/$2/$3/$4/$5/$6/$7/$8/$1$2$3$4$5$6$7$8$9$10.$11 [L] # scenes images RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^scenes/([0-9]+)(\-[_a-zA-Z0-9\s-]*)?/.+?([2-4]x)?\.(gif|jpeg|jpg|png|webp)$ %{ENV:REWRITEBASE}img/scenes/$1$2$3.$4 [L] # scenesthumb images RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^scenesthumb/([0-9]+)(\-[_a-zA-Z0-9\s-]*)?/.+?([2-4]x)?\.(gif|jpeg|jpg|png|webp)$ %{ENV:REWRITEBASE}img/scenes/thumbs/$1$2$3.$4 [L] # stores images RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^stores/([0-9]+)(\-[_a-zA-Z0-9\s-]*)?/.+?([2-4]x)?\.(gif|jpeg|jpg|png|webp)$ %{ENV:REWRITEBASE}img/st/$1$2$3.$4 [L] # suppliers images RewriteCond %{HTTP_HOST} ^chnyc.us$ RewriteRule ^suppliers/([0-9]+)(\-[_a-zA-Z0-9\s-]*)?/.+?([2-4]x)?\.(gif|jpeg|jpg|png|webp)$ %{ENV:REWRITEBASE}img/su/$1$2$3.$4 [L]

Sorry for my confusing question. I meant to ask which files in the Thirty Bees bleeding edge code are used to generate the images. I can do some checking there to help localize the issue. I do have all the original image files appearing in the directories with the generated images. It is only the product images the bleeding edge has problems with. Images for categories are generated properly.