I was stuck with an older version of mailcow from 2017 which was not upgradeable via update.sh, and if you are too you can follow this steps to solve it.

• install the newest mailcow version: https://docs.mailcow.email/de/i_u_m/i_u_m_install/
• recreate all domains and users manualy (todo: create script to do this from maildir via API)
• rsync only the maildir from old installation:

rsync -aHhP --numeric-ids --delete /var/lib/docker/volumes/mailcowdockerized_vmail-vol-1/_data/ root@host:/var/lib/docker/volumes/mailcowdockerized_vmail-vol-1/_data

• use the importer.sh script to import all emails to the corresponding email-address directly in the container:

#!/bin/bash

# Define the parent path of the Maildir
MAILDIR_PARENT="/var/vmail"

# Get all users from doveadm
USERS=$(doveadm user '*')

# Loop through each user
for FULL_USER in $USERS; do
    # Extract domain and username
    DOMAIN=$(echo "$FULL_USER" | cut -d@ -f2)
    USER=$(echo "$FULL_USER" | cut -d@ -f1)

    # Construct the path to the user's Maildir
    USER_MAILDIR="${MAILDIR_PARENT}/${DOMAIN}/${USER}"

    # Check if the Maildir exists
    if [ -d "$USER_MAILDIR" ]; then
        echo "Processing $USER_MAILDIR"

        # Insert your command to import mails from the user's Maildir
        # For example, using doveadm import (adjust as necessary):
        doveadm import -u $FULL_USER maildir:$USER_MAILDIR "" all

        # Replace the above line with your actual command for importing mails.
    else
        echo "Maildir not found for $FULL_USER"
    fi
done

I made a Github repo, so you can download the importer script here: https://github.com/gweit/mailcow-importer

This should also work for non-mailcow installations, as long as the folder structure is dovecot-like.

When you use Server Side Rendering (SSR) in your Vue project with webpack or some other tool you might see your code doubled down. As this can be caused by adding external Javascript Sources to your Headers here´s a little Workaround.

By using this plugin (https://github.com/chrisvfritz/prerender-spa-plugin) you can add your script after rendering:

const path = require('path')
const PrerenderSPAPlugin = require('prerender-spa-plugin')
const PuppeteerRenderer = PrerenderSPAPlugin.PuppeteerRenderer
const iubenda = '<script type="text/javascript" src="//cdn.iubenda.com/cs/iubenda_cs.js" charset="UTF-8" async></script><script type="text/javascript">var _iub = _iub || [];_iub.csConfiguration = {"consentOnContinuedBrowsing":false,"whitelabel":false,"lang":"it","siteId":<your_id>,"floatingPreferencesButtonColor":"#010101","floatingPreferencesButtonCaptionColor":"#ffffff","logLevel":"noLog","askConsentAtCookiePolicyUpdate":true,"countryDetection":true,"gdprAppliesGlobally":false,"cookiePolicyId":<your_id>, "banner":{ "customizeButtonDisplay":true,"customizeButtonColor":"#ffffff","customizeButtonCaptionColor":"#333333","rejectButtonColor":"#0073CE","rejectButtonCaptionColor":"white","position":"float-bottom-center","textColor":"white","backgroundColor":"#ff0132","acceptButtonDisplay":true,"acceptButtonColor":"#222222","acceptButtonCaptionColor":"white" }};</script>'

module.exports = {
  pages: {
    index: {
      entry: 'src/main.js',
      title: 'Title'
    }
  },
  pwa: {
    name: 'Cool App',
    themeColor: '#4DBA87',
    msTileColor: '#000000',
    appleMobileWebAppCapable: 'yes',
    appleMobileWebAppStatusBarStyle: 'black',
    iconPaths: {
		favicon32: 'icons/android/icon_36.png',
		favicon16: 'icons/android/icon_36.png',
		appleTouchIcon: 'icons/ios/icon_152.png'
	}
  },
  configureWebpack:  {
    plugins: process.env.NODE_ENV === 'production' ? [
      new PrerenderSPAPlugin({
        // Required - The path to the webpack-outputted app to prerender.
        staticDir: path.join(__dirname, 'dist'),
        // Required - Routes to render.
        postProcess (context) {
          const bodyEnd = context.html.indexOf('</body>')
          context.html = context.html.substr(0, bodyEnd) + iubenda + context.html.substr(bodyEnd)

          return context
        },
        routes: [ '/'],
        renderer: new PuppeteerRenderer({
          renderAfterTime: 4000
        })
      })
    ] : []
  }
}

Photo by Pankaj Patel on Unsplash

Some of you using Prestashop might wonder why their copied and pasted Content might not be saved.

This can be caused by a simple 0 in Setting -> Article -> max length of Description.

Simply change this with a value that is comfortable for you and copy & paste should work as expected.

Photo by Bench Accounting on Unsplash

Sometimes you need to keep your Mac runing, allthough you are not there.

Normally it would go in Sleep Mode, but you might need to download something big or keep your Dropbox syncing - so there´s a little Trick you can use.

If you are handy in your Terminal this is very easy, but also if not - this will make your Day ;)

• Open a Terminal Window on your Mac
• type in the following:

caffeinate

This will execute some kind of "placeholder execution" while you are not there.

If you know how long the Process will be needed you can use this one:

caffeinate -t 3600

where the number indicates the Time of Execution. Once passed the process will close and your Mac will go to sleep if there´s no further Action.

To Shut down your Monitor/s in the Meantime use this one:

Ctrl + Shift + Eject

Photo by Jay Wennington on Unsplash

If you've ever been in a Situation where you have to meet a property for every class beginning or ending the same this is how you can get it done.

Lets assume we have Bootstrap as our Ground-Framework because we like the Grid or the Aligning or all the Buttons or What-so-ever:

remove padding from all the .col

div[class*=col] {
	padding: 0;
}

Photo by Greg Rakozy on Unsplash

For anyone using the Revolution Slider in Prestashop and wants to get multilanguage Support in his Slides!

You can achieve this by following these Steps:

• Activate Multilanguage Support for the Slider
• go to Slides List
• click on the Pencil and set the Language for the Slide
• now you can set/change the Content and it will only be shown for the choosen Language

Best, Gernot ;)

Photo by Igor Miske on Unsplash

Well, because it is:

• clean
• fast
• smooth
• very well done
• great UX and UI
• packed with all you need

and it has:

• a big Comunity
• lot of Potential
• not to much Muscles to keep runing
• great Developers in the Back
• a persistent Update Cycle

so much said i like it because:

• i can write (and style) without my Mouse (yes, i miss you to...)
• did i mention it's very fast?
• it keeps me focused

Hmm..., but there are also some Cons of course:

• Installation
• Maintenance
• Updates
• Templating and Theming

Next Up: How to start

Photo by Andrew Neel on Unsplash

In my daily Routine of getting updated on what's hot and (sometimes) deprecated, i found this node.js based CMS called Apostrophe.

Trying to do some Templating you can see my Tentatives right on sandbox.

Photo by Glenn Carstens-Peters on Unsplash

Usually when you install a new Theme in Prestashop there are some Modules installed to.

Normally after uploading the Theme you'll see a List of it added, activated and deactivated.

Recently i installed a Theme which uses the Revolution Slider. Unfortunaely after the Activation the Settings were a little messed up, and Chrome Log showed some Errors.

Solution

• deacivate all Sliders
• deactivate Revolution Slider
• reactivate Revolution Slider

Now everything should work as expected.

If not feel free to drop me a line on support@superswitch.co - i can take a look and maybe help you out ;)

Photo by Headway on Unsplash

When this happen try to check if your Password is coherent with the one in /config/settings.inc.php .

Sometimes when you use special Character in your Passwords the Upgrade Script interprets this not very well.

Photo by John Baker on Unsplash

Recently i had a small Problem with Skrollr. It didn't work on Mobile and Touch by hiding the Skroll Bar.

The sweet Hint is to wrap all your scrollable Content into a DIV with the ID skrollr-body.

<div id="skrollr-body">

</div>

If you entire Site is to scroll so you can apply this also to the body Element, but if you have a sticky Navbar (Bootstrap or something similar) you have to exlude the Navigation by wrapping your Content in the DIV described above.

Photo by William Iven on Unsplash

I guess a lot of you knows about this little snatchy Thing, that happens when you use Bootstraps Affix in Order to get something sticky when it hits a given Point on your Website.

The Rest of your Content makes a little (or sometimes big) Jump upwards...

By reading this i can assure you that i tried a lot of different Approaches to get this running smooth and clean, like custom jQuery to get Viewports Height and Width, to use on other custom Scripts which calculates how much Jump there will be when my second bar hits the Top of my Page, and so on and on and on, until the End of our Days. But lets break it down: - nothing worked very well.

• custom jQuery and Bootstrap-.js Coding will slow down you Site as there will be a lot of stuff calculated Client-Side
• Custom .css may drive you nuts o.O

So i did it simple and nice (after a few Days of struggle of course):

Wrapping Containers - yes, this is the magic Word!

I guess you know the Height of your to-affix-element? Ok, then lets wrap a Container (a div for example) around it which has the exact Height of your to-affix-element. This will prevent the Rest of the Site to jump when the Affix removes the to-affix-element from the DOM.

.css

nav {
  height: 80px;
  width: 100%;
}

.nav-container {
  height: 80px;
  width: 100%;
  display: table;
}

html

<div class="nav-container" data-spy="affix" data-offset-top="60" data-offset-bottom="200">
<nav>

</nav>
</div>

js

 $('nav').affix({
    offset: {
    top: 100,
    bottom: function () {
    return (this.bottom = $('.footer').outerHeight(true))
    }
   }
  })

Photo by Goran Ivos on Unsplash