Lots of module releases

[Traumflug]

In the upcoming days, a whole lot of releases of existing modules are planned. Sometimes just code maintenance, sometimes substantial improvements. I'll post release notes here, so you don't have to look up all of them on Github.

Today it's Core Updater:

• Make the Ignore community themes switch aware of the new community theme, Niara.
• Substantial performance improvement when scanning large sets of (product) images. Some hosts simply timed out when searching 100,000 product images, making updates impossible.
• Code maintenance.

 

coreupdater-v1.1.0.zip

(also arriving in your back office)

[Traumflug]

These are all just code maintenance releases:

• bankwire
• blockbanner
• blockbestsellers
• blockcategories
• blockcms
• blockcmsinfo
• blockcontact
• blockcontactinfos
• blockcurrencies
• blockcustomerprivacy
• blockfacebook

These have additional fixes:

• blockcart: support for properly rounded prices

 

... to be continued tomorrow.

[the.rampage.rado]

They are not visible as updates in Modules. Also coreupdater disapeared. Yesterday I was able to update one of my shops but today it's missing from the rest.

[Traumflug]

True, I forgot to upload the famous all.json. Corrected a minute ago.

[movieseals]

Seems like the blockbanner module will not update - it keeps the yellow button requesting an update no matter what I do.  All the others updated flawlessly.

[AndyC]

Both sites all updated fine ..How do we find out what changes were made

 

[Traumflug]

1 hour ago, AndyC said:

How do we find out what changes were made

By looking up each modules' repository. It's Open Source!

https://github.com/thirtybees

[Traumflug]

On 6/27/2019 at 10:37 PM, Traumflug said:

... to be continued tomorrow.

Obviously this didn't happen. The day after the 1.1.0 preview publication some 20-30 commits appeared in the repo. If I build a distribution package with this, I get this for the shop front page ...

... so I'm kind of back to square one.

 

Building a distribution package for previews and testing this goes like this:

./build.sh --no-validate HEAD

 

[wakabayashi]

@Traumflug I am not sure, if I understand you right. But this issue is well known: https://github.com/thirtybees/thirtybees/issues/749

[alwayspaws]

I've had the camera image for bookmarks on my phone all along. I just gave up on it. 

[Traumflug]

The camera image is --you guessed it-- a placeholder image. Nice thing is, it gets delivered for the original URL. Which means, one can look up the URL of each camera image (they likely have distinct URLs) to find out what's missing.

[movieseals]

I had this problem before.  To simplify your life, use this script:

 

<?php
/*prepare list of broken images*/
require(dirname(__FILE__).'/config/config.inc.php'); //  you might need to change the path to the file 'config.inc.php' if you are not in the root folder
$id_lang = 1; //getting links for one language. This is enough to identify empty images
$i = 0;
$limit = 100;
$filename = 'broken_urls.txt';
file_put_contents($filename, '', LOCK_EX); //remove old content
//file_put_contents($filename, '', FILE_APPEND | LOCK_EX); //append content
do {
    $images = Db::getInstance()->executeS('
        select *
        from `'._DB_PREFIX_.'image` i
        limit ' . (int)($i++ * $limit) . ', ' . (int)$limit . '
    '); //receiving the stack of images

    foreach ($images as $image) {
        $imgObj = new Image($image['id_image'], $id_lang);
        $image_path = _PS_PROD_IMG_DIR_ . $imgObj->getImgPath() . '.' . $imgObj->image_format;
        if (!file_exists($image_path)) { //verifying, whether the file with the image exists
            $productObj = new Product($image['id_product'], NULL, $id_lang); //creating a product object for link generation

            print_r($image['id_product'] . ' => ' . Context::getContext()->link->getImageLink($productObj->link_rewrite, $image['id_image']) . chr(10)); //die;
            file_put_contents($filename, $image['id_product'] . ' => ' . Context::getContext()->link->getImageLink($productObj->link_rewrite, $image['id_image']) . chr(10), FILE_APPEND | LOCK_EX);
            echo '<br>';
        }
    }
} while(count($images));
      echo 'success';

?>

By visiting the script (saved as a PHP file - I call mine broken_image_TB.php), the script will generate a text file called broken_urls.  You can then go and fix them.

[Traumflug]

These are all code maintenance releases:

• homeslider
• homefeatured
• vatnumber
• trackingfront
• producttooltip
• productscategory
• productpaymentlogos
• blocknewsletter
• blockmanufacturer
• blocklink
• blocksearch
• blocksharefb
• blocktags
• blockviewed
• ecbexchange
• crossselling
• dashgoals
• dashactivity
• dashproducts
• dashtrends
• socialsharing
• statsdata
• sendtoafriend

These have additional fixes/changes:

• homeslider: new images for thirty bees 1.1.0.
• homefeatured: A distinct template for the tab on the home page, views/templates/hook/homefeatured_home.tpl. Default is compatible with theme community-theme-default. As with all templates, this can get overridden by the theme, but doesn't have to.

Most of the releases in the list above were actually done by @datakick, big THANK YOU to him!

 

[Traumflug]

Aaaand ... yet another chunk.

These are all just code maintenance releases:

• ctconfiguration
• blocklanguages
• blockmyaccount
• blockmyaccountfooter
• blockpaymentlogo
• blockpermanentlinks
• blockreinsurance
• blockspecials
• blocktopmenu
• blockuserinfo
• tbupdater
• themeconfigurator
• blocklayered

These have additional fixes:

• blocklayered: Fixed a retrocompatibility bug, settings from earlier versions should work now. Thanks to @Captain-FLAM!
• blocktopmenu: New feature to limit the menu level depth. It defaults to 2. Thanks to @pauld-codes!
• tbupdater: Disable the configuration page. Merchants should (and can) no longer update thirty bees core with this module. There is now Core Updater. Nevertheless, tbupdater should stay installed, it's still needed for module updates.
• tbupdater: Upgrade to the new version on thirty bees 1.0.8 or later, only. To allow merchants to still update to thirty bees 1.0.8 using the previous version.

Cheers!

[SLiCK_303]

wow....thanks for the hard work guys!!

[DRMasterChief]

Seems that i have to setup an 1.1.0  installation,  even the 1.0.7 is not live   

A big thank you from here, too.  Looks like it is growing good and into the right direction !!! 

[Briljander]

Great work! Seems like you have put in another gear. 

[Traumflug]

On 7/6/2019 at 9:43 PM, DRMasterChief said:

Seems that i have to setup an 1.1.0  installation,  even the 1.0.7 is not live

All these releases should appear in 1.0.7 and earlier as well, except for tbupdater.

[Traumflug]

Here's the last chunk for the time being:

• beesblog
  • Changed default image sizes.
  • Removed Google+ support, this community vanished.
  • Added support for updateFriendlyURL().
  • Code maintenance.
• blockbestsellers
  • Actually two releases, 2.2.0 and 2.2.1. The latter restores compatibility with community-theme-default and themes derived from this.
  • Support for the new hook displayHome.
  • Shows just 4 products by default to appear more pleasing on theme Niara.
  • Code maintenance.
• blockcontactinfos
  • Preserve newlines in the contact address. Before one could enter them on the configuration page, but front office would show all in one line.
• blocknewproducts: same as with module blockbestsellers.
• blocksocial
  • Pre-fill some fields on installation.
  • Code maintenance.
• blockstore
  • Code maintenance.
• blocksupplier
  • Code maintenance.
• coreupdater (yet another release)
  • Fix configuration page display on wide screens.
• homeslider (yet another release)
  • Explain image sizes on the configuration page.
• statsmodule
  • Additional section Stats for Groups.
  • Fixed uninstallation.
  • Code maintenance.

And last, not least, a new module: HTML Block.