Liebling is a beautiful and clean Ghost theme that is easy and comfortable to use.

  • By Eduardo GΓ³mez
  • Last update: Jan 2, 2023
  • Comments: 17

Liebling

Liebling is a beautiful and clean Ghost theme that is easy and comfortable to use. It's free and you can use it for any kind of content you might have. Now with dark mode πŸŒ“ !

If you find this theme useful, please consider to make a donation to support its development! πŸ™πŸΌ

Donate

Ghost 5

This theme has been optimized for Ghost 5, if you are looking for a Ghost 4 compatible version please refer to this link.

Preview

You can see a live demo here: https://liebling.eduardogomez.io



Download

To get the latest version please head over the releases page and download the file liebling.zip of the latest release.

Documentation

To know how to enable the search, comments, newsletter and more, please head to the Wiki.

Features

General features

  • Clean and beautiful design
  • Lightning fast
  • Lightweight and high performance
  • Fully responsive, looks great on any device
  • Compatible with modern browsers

Ghost features

  • Subscription form
  • Multiple authors
  • Logo support
  • Secondary menu
  • Accent color
  • Featured posts and pages
  • Post, Page, Tag, Authors, pages
  • Koenig editor
  • Bookmark card
  • Gallery card
  • Button card
  • NFT card
  • Callouts
  • Toggles
  • Quotes
  • Products
  • Audio
  • Video
  • File uploads
  • Headers
  • Blog title and description
  • Cover image for Home, Post, Page, Tag, Author pages
  • Author avatar, bio, location, website and social links
  • Facebook and Twitter social links
  • Reading time
  • Next and Previous post navigation
  • Primary tag in posts

Liebling unique features

  • Dark mode
  • Search
  • Custom settings
  • Custom Subscribe page
  • Custom authors page
  • Custom error page
  • Medium style image zoom
  • Comments with Disqus
  • Share post on Facebook and Twitter
  • Slider for featured posts
  • Support for normal, wide and full images in posts
  • Reading progress indicator
  • RTL language support

Localization

Tests performed

  • W3C Markup Validation: Correct validation
  • Ghost GScan: 100/100 points
  • GTmetrix PageSpeed Score: A (97%)
  • PageSpeed Insights: 94/100 (mobile) 99/100 (desktop)
  • Pingdom Performance Grade: A 91

Theme development

Thanks to D3473R πŸ’ͺ🏼 for creating a development environment with Docker. From now on you can work on this theme without installing a Ghost instance on your local machine. With two commands you have an instant development setup and you can build the theme for production.

Please take a look to this page to see how it works: https://github.com/eddiesigner/liebling/wiki/Theme-development-with-Docker

Help and Support

If you have any questions or troubles with this product, please feel free to open an issue here.

Contributing

Contributions are very welcome. First, please read the Pull Request Guidelines on the wiki.

Related

  • Galerie - Modern and versatile theme that stands out for its sleek design, it's incredibly fast, it offers a great user experience and it has many options to customise it.

  • Firma - Ghost theme that can be used by startups to large companies to publish any kind of articles related to their business. It stands out for its clean design and is able to adapt to any company's identity.

  • Weiss Pro - Modern and beautiful Ghost theme ready to make your content shine.

License

Copyright (c) 2019-present Eduardo GΓ³mez. Released under the MIT license.

Credits

All the photos I used in this theme were taken from Unsplash

Github

https://github.com/eddiesigner/liebling

Comments(17)

  • 1

    Support members feature from Ghost 3.0

    With the release of Ghost 3.0 we now have the capability for member login. Though there are many aspects to consider to fully support the membership feature in a theme, the logical start could be with the basic setup for signin/signup forms that would allow the sites to let users register on their websites. I was able to get it working without any styles etc, by just creating a page from Ghost admin with following embedded html.

    <form data-members-form>
      <input data-members-email type="email" required="true"/>
      <button type="submit">Continue</button>
    </form>
    

    The following would be great to have as the first steps.

    • Login/logout button if member feature is enabled
    • Styled singin/signup pages
  • 2

    Mobile score is 70 instead of 90+

    Hello,

    Congrats for your awesome ghost theme. But I have one question.

    I need a fast theme and casper scores 90+ on mobile. Your theme scores 70 on mobile (even though I used to be around 85, I don't know why it went down). https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fsoundsirius.digitalpress.blog%2F&tab=desktop

    Please help me make your theme score 90+ on mobile on my website. https://soundsirius.digitalpress.blog/

  • 3

    Add local css file to theme leads to 'failed to read zip file' when uploading it

    Hello,

    I've been trying to add the prism.js js and css to the theme with no success, leading over and over to the error 'Failed to read zip file' when uploading the zip.

    I have added the correct tags to the default.hbs for the style and the script, like this :

    <link rel="stylesheet" type="text/css" href="{{asset "css/prism.css"}}" media="screen" />
    <script type="text/javascript" src="{{asset "js/prism.js"}}"></script>
    

    I have put the files respectively into assets/js/prism.js and assets/css/prism.css

    I zip it, upload it : Error: Failed to read the zip file. Once I remove the prism.js and prism.css files, no more problem. Am I not zipping it right ? Do I have to build something ? Do I have to edit somewhere that I added a new file ?

    Thank you.

  • 4

    Add syntax highlights

    Hi, thanks for the theme. Unfortunately, it doesn't have a very popular feature: Syntax highlighting.
    Other themes usually use Prism for this. What your thoughts on this?

  • 5

    Remove all build assets from git and fix windows build issues

    Hi,

    i removed and untracked all {js|css|font} files that are build with our CI pipeline anyway. Also there were some build issues on windows if no python version 2 is installed. (I am now using the build aos tarball instead of building it again with our pipeline) There is also an open PR in run-script-os which fixes another build error. So for now I switched to the forked repo, we can switch back to the original if the PR gets merged.

    Regards, D3473R

  • 6

    Blogpost Image is resized weirdly on mobile

    Link: https://merecivilian.com/spotify-connect-on-homepod/ https://merecivilian.com/hannibal/

    If you open this image in mobile, the image looks weird. Plus, the resizing on the desktop is also weird. It appears to crop it. I am not sure what exactly it is doing, but the images were fine when used with my previous ghost theme.

    Also, if you go to the home page, https://merecivilian.com/, the images load fine and is complete. When the actual post is opened, the image goes weird.

    Can you please have a look?

  • 7

    Docker stuck in a loop

    Hi I have just downloaded v0.5.2 and tried the docker image on (MacOS Mojave) but after following the steps and running docker-watch it opens the localhost:3001 page in the browser and the page just keeps loading, also in the terminal the "browser reloading" event just keeps stacking up. i.e.

    [Browsersync] Reloading Browsers... (buffered 79 events)

    I guess it keeps seeing changes and therefore never finishes?

    Does anyone know what might be the problem? I haven't changed anything to the files inside the zip.

  • 8

    Local theme development: `Unable to run migrations`

    Hi,

    I followed the instructions here: https://github.com/eddiesigner/liebling/wiki/Theme-development-with-Docker

    But I get the following error:

    [DOCKER] Attaching to ghost
    [DOCKER] ghost    | [2022-08-12 09:39:59] INFO Ghost is running in development...
    [DOCKER] ghost    | [2022-08-12 09:39:59] INFO Listening on: :::2368
    [DOCKER] ghost    | [2022-08-12 09:39:59] INFO Url configured as: http://localhost:2368/
    [DOCKER] ghost    | [2022-08-12 09:39:59] INFO Ctrl+C to shut down
    [DOCKER] ghost    | [2022-08-12 09:39:59] INFO Ghost server started in 2.114s
    [DOCKER] ghost    | [2022-08-12 09:40:00] WARN Database state requires migration.
    [DOCKER] ghost    | [2022-08-12 09:40:01] INFO Creating database backup
    [DOCKER] ghost    | [2022-08-12 09:40:01] INFO Database backup written to: /var/lib/ghost/content/data/liebling.ghost.2022-08-12-09-40-01.json
    [DOCKER] ghost    | [2022-08-12 09:40:01] INFO Running migrations.
    [DOCKER] ghost    | [2022-08-12 09:40:01] INFO Rolling back: Unable to run migrations.
    [DOCKER] ghost    | [2022-08-12 09:40:01] INFO Rollback was successful.
    [DOCKER] ghost    | [2022-08-12 09:40:01] ERROR Unable to run migrations
    [DOCKER] ghost    | 
    [DOCKER] ghost    | Unable to run migrations
    [DOCKER] ghost    | 
    [DOCKER] ghost    | "You must be on the latest v2.x to update across major versions - https://ghost.org/docs/update/"
    [DOCKER] ghost    | "Run 'ghost update v2' to get the latest v2.x version, then run 'ghost update' to get to the latest."
    [DOCKER] ghost    | 
    [DOCKER] ghost    | Error ID:
    [DOCKER] ghost    |     bc7b4980-1a22-11ed-91ea-3bed1453e266
    [DOCKER] ghost    | 
    [DOCKER] ghost    | ----------------------------------------
    [DOCKER] ghost    | 
    [DOCKER] ghost    | InternalServerError: Unable to run migrations
    [DOCKER] ghost    |     at /var/lib/ghost/versions/5.2.3/node_modules/knex-migrator/lib/index.js:1032:19
    [DOCKER] ghost    |     at up (/var/lib/ghost/versions/5.2.3/core/server/data/migrations/utils/migrations.js:118:19)
    [DOCKER] ghost    |     at Object.up (/var/lib/ghost/versions/5.2.3/core/server/data/migrations/utils/migrations.js:54:19)
    [DOCKER] ghost    |     at /var/lib/ghost/versions/5.2.3/node_modules/knex-migrator/lib/index.js:982:33
    [DOCKER] ghost    |     at /var/lib/ghost/versions/5.2.3/node_modules/knex/lib/execution/transaction.js:221:22
    [DOCKER] ghost    | 
    [DOCKER] ghost    | [2022-08-12 09:40:01] WARN Ghost is shutting down
    [DOCKER] ghost    | [2022-08-12 09:40:01] WARN Ghost has shut down
    [DOCKER] ghost    | [2022-08-12 09:40:01] WARN Ghost was running for a few seconds
    [DOCKER] ghost exited with code 2
    

    Any help would be greatly appreciated. Also, please let me know if there is any more information I can provide :)

    Thank you so much!

  • 9

    npm install fails

    • Downloaded master
    • Unpacked
    • Ran npm install in src as per instructions
    β”Œβ”€[[email protected]][~/Dev/web/liebling-master/src]
    └──β–ͺ npm install
    npm ERR! code 1
    npm ERR! git dep preparation failed
    npm ERR! command /usr/bin/node /usr/local/lib/node_modules/npm/bin/npm-cli.js install --force --cache=/home/sgofferj/.npm/_cacache --prefer-offline=false --prefer-online=false --offline=false --no-progress --no-save --no-audit
    npm ERR! npm WARN using --force Recommended protections disabled.
    npm ERR! npm ERR! code 1
    npm ERR! npm ERR! path /home/sgofferj/.npm/_cacache/tmp/git-clone-d5dba9ce/node_modules/node-sass
    npm ERR! npm ERR! command failed
    npm ERR! npm ERR! command sh -c node scripts/build.js
    npm ERR! npm ERR! Building: /home/sgofferj/node_modules/node/bin/node /home/sgofferj/.npm/_cacache/tmp/git-clone-d5dba9ce/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
    npm ERR! npm ERR! make: Entering directory '/home/sgofferj/.npm/_cacache/tmp/git-clone-d5dba9ce/node_modules/node-sass/build'
    npm ERR! npm ERR!   g++ '-DNODE_GYP_MODULE_NAME=binding' '-DUSING_UV_SHARED=1' '-DUSING_V8_SHARED=1' '-DV8_DEPRECATION_WARNINGS=1' '-DV8_DEPRECATION_WARNINGS' '-DV8_IMMINENT_DEPRECATION_WARNINGS' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-D__STDC_FORMAT_MACROS' '-DOPENSSL_NO_PINSHARED' '-DOPENSSL_THREADS' '-DBUILDING_NODE_EXTENSION' -I/home/sgofferj/.node-gyp/15.10.0/include/node -I/home/sgofferj/.node-gyp/15.10.0/src -I/home/sgofferj/.node-gyp/15.10.0/deps/openssl/config -I/home/sgofferj/.node-gyp/15.10.0/deps/openssl/openssl/include -I/home/sgofferj/.node-gyp/15.10.0/deps/uv/include -I/home/sgofferj/.node-gyp/15.10.0/deps/zlib -I/home/sgofferj/.node-gyp/15.10.0/deps/v8/include -I../../nan  -fPIC -pthread -Wall -Wextra -Wno-unused-parameter -m64 -O3 -fno-omit-frame-pointer -fno-rtti -fno-exceptions -std=gnu++1y -std=c++0x -MMD -MF ./Release/.deps/Release/obj.target/binding/src/binding.o.d.raw   -c -o Release/obj.target/binding/src/binding.o ../src/binding.cpp
    npm ERR! npm ERR! make: Leaving directory '/home/sgofferj/.npm/_cacache/tmp/git-clone-d5dba9ce/node_modules/node-sass/build'
    npm ERR! npm ERR! gyp info it worked if it ends with ok
    npm ERR! npm ERR! gyp verb cli [
    npm ERR! npm ERR! gyp verb cli   '/home/sgofferj/node_modules/node/bin/node',
    npm ERR! npm ERR! gyp verb cli   '/home/sgofferj/.npm/_cacache/tmp/git-clone-d5dba9ce/node_modules/node-gyp/bin/node-gyp.js',
    npm ERR! npm ERR! gyp verb cli   'rebuild',
    npm ERR! npm ERR! gyp verb cli   '--verbose',
    npm ERR! npm ERR! gyp verb cli   '--libsass_ext=',
    npm ERR! npm ERR! gyp verb cli   '--libsass_cflags=',
    npm ERR! npm ERR! gyp verb cli   '--libsass_ldflags=',
    npm ERR! npm ERR! gyp verb cli   '--libsass_library='
    npm ERR! npm ERR! gyp verb cli ]
    npm ERR! npm ERR! gyp info using [email protected]
    npm ERR! npm ERR! gyp info using [email protected] | linux | x64
    npm ERR! npm ERR! gyp verb command rebuild []
    npm ERR! npm ERR! gyp verb command clean []
    npm ERR! npm ERR! gyp verb clean removing "build" directory
    npm ERR! npm ERR! gyp verb command configure []
    npm ERR! npm ERR! gyp verb check python checking for Python executable "python2" in the PATH
    npm ERR! npm ERR! gyp verb `which` succeeded python2 /usr/bin/python2
    npm ERR! npm ERR! gyp verb check python version `/usr/bin/python2 -c "import sys; print "2.7.18
    npm ERR! npm ERR! gyp verb check python version .%s.%s" % sys.version_info[:3];"` returned: %j
    npm ERR! npm ERR! gyp verb get node dir no --target version specified, falling back to host node version: 15.10.0
    npm ERR! npm ERR! gyp verb command install [ '15.10.0' ]
    npm ERR! npm ERR! gyp verb install input version string "15.10.0"
    npm ERR! npm ERR! gyp verb install installing version: 15.10.0
    npm ERR! npm ERR! gyp verb install --ensure was passed, so won't reinstall if already installed
    npm ERR! npm ERR! gyp verb install version is already installed, need to check "installVersion"
    npm ERR! npm ERR! gyp verb got "installVersion" 9
    npm ERR! npm ERR! gyp verb needs "installVersion" 9
    npm ERR! npm ERR! gyp verb install version is good
    npm ERR! npm ERR! gyp verb get node dir target node version installed: 15.10.0
    npm ERR! npm ERR! gyp verb build dir attempting to create "build" dir: /home/sgofferj/.npm/_cacache/tmp/git-clone-d5dba9ce/node_modules/node-sass/build
    npm ERR! npm ERR! gyp verb build dir "build" dir needed to be created? /home/sgofferj/.npm/_cacache/tmp/git-clone-d5dba9ce/node_modules/node-sass/build
    npm ERR! npm ERR! gyp verb build/config.gypi creating config file
    npm ERR! npm ERR! gyp verb build/config.gypi writing out config file: /home/sgofferj/.npm/_cacache/tmp/git-clone-d5dba9ce/node_modules/node-sass/build/config.gypi
    npm ERR! npm ERR! gyp verb config.gypi checking for gypi file: /home/sgofferj/.npm/_cacache/tmp/git-clone-d5dba9ce/node_modules/node-sass/config.gypi
    npm ERR! npm ERR! gyp verb common.gypi checking for gypi file: /home/sgofferj/.npm/_cacache/tmp/git-clone-d5dba9ce/node_modules/node-sass/common.gypi
    npm ERR! npm ERR! gyp verb gyp gyp format was not specified; forcing "make"
    npm ERR! npm ERR! gyp info spawn /usr/bin/python2
    npm ERR! npm ERR! gyp info spawn args [
    npm ERR! npm ERR! gyp info spawn args   '/home/sgofferj/.npm/_cacache/tmp/git-clone-d5dba9ce/node_modules/node-gyp/gyp/gyp_main.py',
    npm ERR! npm ERR! gyp info spawn args   'binding.gyp',
    npm ERR! npm ERR! gyp info spawn args   '-f',
    npm ERR! npm ERR! gyp info spawn args   'make',
    npm ERR! npm ERR! gyp info spawn args   '-I',
    npm ERR! npm ERR! gyp info spawn args   '/home/sgofferj/.npm/_cacache/tmp/git-clone-d5dba9ce/node_modules/node-sass/build/config.gypi',
    npm ERR! npm ERR! gyp info spawn args   '-I',
    npm ERR! npm ERR! gyp info spawn args   '/home/sgofferj/.npm/_cacache/tmp/git-clone-d5dba9ce/node_modules/node-gyp/addon.gypi',
    npm ERR! npm ERR! gyp info spawn args   '-I',
    npm ERR! npm ERR! gyp info spawn args   '/home/sgofferj/.node-gyp/15.10.0/include/node/common.gypi',
    npm ERR! npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
    npm ERR! npm ERR! gyp info spawn args   '-Dvisibility=default',
    npm ERR! npm ERR! gyp info spawn args   '-Dnode_root_dir=/home/sgofferj/.node-gyp/15.10.0',
    npm ERR! npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/home/sgofferj/.npm/_cacache/tmp/git-clone-d5dba9ce/node_modules/node-gyp',
    npm ERR! npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/sgofferj/.node-gyp/15.10.0/<(target_arch)/node.lib',
    npm ERR! npm ERR! gyp info spawn args   '-Dmodule_root_dir=/home/sgofferj/.npm/_cacache/tmp/git-clone-d5dba9ce/node_modules/node-sass',
    npm ERR! npm ERR! gyp info spawn args   '-Dnode_engine=v8',
    npm ERR! npm ERR! gyp info spawn args   '--depth=.',
    npm ERR! npm ERR! gyp info spawn args   '--no-parallel',
    npm ERR! npm ERR! gyp info spawn args   '--generator-output',
    npm ERR! npm ERR! gyp info spawn args   'build',
    npm ERR! npm ERR! gyp info spawn args   '-Goutput_dir=.'
    npm ERR! npm ERR! gyp info spawn args ]
    npm ERR! npm ERR! gyp verb command build []
    npm ERR! npm ERR! gyp verb build type Release
    npm ERR! npm ERR! gyp verb architecture x64
    npm ERR! npm ERR! gyp verb node dev dir /home/sgofferj/.node-gyp/15.10.0
    npm ERR! npm ERR! gyp verb `which` succeeded for `make` /usr/bin/make
    npm ERR! npm ERR! gyp info spawn make
    npm ERR! npm ERR! gyp info spawn args [ 'V=1', 'BUILDTYPE=Release', '-C', 'build' ]
    npm ERR! npm ERR! In file included from ../src/binding.cpp:3:
    npm ERR! npm ERR! ../src/sass_context_wrapper.h:8:10: fatal error: sass/context.h: No such file or directory
    npm ERR! npm ERR!     8 | #include <sass/context.h>
    npm ERR! npm ERR!       |          ^~~~~~~~~~~~~~~~
    npm ERR! npm ERR! compilation terminated.
    npm ERR! npm ERR! make: *** [binding.target.mk:126: Release/obj.target/binding/src/binding.o] Error 1
    npm ERR! npm ERR! gyp ERR! build error 
    npm ERR! npm ERR! gyp ERR! stack Error: `make` failed with exit code: 2
    npm ERR! npm ERR! gyp ERR! stack     at ChildProcess.onExit (/home/sgofferj/.npm/_cacache/tmp/git-clone-d5dba9ce/node_modules/node-gyp/lib/build.js:262:23)
    npm ERR! npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:378:20)
    npm ERR! npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)
    npm ERR! npm ERR! gyp ERR! System Linux 5.4.0-67-generic
    npm ERR! npm ERR! gyp ERR! command "/home/sgofferj/node_modules/node/bin/node" "/home/sgofferj/.npm/_cacache/tmp/git-clone-d5dba9ce/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
    npm ERR! npm ERR! gyp ERR! cwd /home/sgofferj/.npm/_cacache/tmp/git-clone-d5dba9ce/node_modules/node-sass
    npm ERR! npm ERR! gyp ERR! node -v v15.10.0
    npm ERR! npm ERR! gyp ERR! node-gyp -v v3.8.0
    npm ERR! npm ERR! gyp ERR! not ok 
    npm ERR! npm ERR! Build failed with error code: 1
    npm ERR! 
    npm ERR! npm ERR! A complete log of this run can be found in:
    npm ERR! npm ERR!     /home/sgofferj/.npm/_cacache/_logs/2021-03-18T12_11_51_515Z-debug.log
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /home/sgofferj/.npm/_logs/2021-03-18T12_11_52_953Z-debug.log
    
  • 10

    Laravel Mix keeps rebuilding in development container

    So just spend this whole day fixing this issue on my machine 😒 Thought I might give you guys the solution if anybody is facing the same issue. Because of something, my ghost container was having issues with the files in the .git folder of this project. You can test this by running

    docker-compose up
    

    in the src folder. If you see chown issues with files in the .git folder, you are facing the same issue as I did. The solution was for me to overwrite it with the .git folder from my src folder. You can do that with the following addition to the docker-compose.yml file:

        volumes:
          - .git:/var/lib/ghost/content/themes/liebling/.git:Z
          - ./..:/var/lib/ghost/content/themes/liebling:Z
          - ./ghost.db:/var/lib/ghost/content/data/ghost.db:Z
    

    Of course, you could also just link to any .git folder that is empty.

  • 11

    Add additional social media icons

    I've added a bunch of social media icons via the Icomoon font generator to be used in the footer when secondary navigation is specified via the Ghost Admin interface in Ghost V3. E.g. if there is an entry in the secondary navigation tab with Label Instagram and URL http://example.org, an icon with the Instagram logo that links to http://example.org is shown in the footer of the page.

    There are still some problems, that I am currently unable to resolve:

    • ~~If an unknown label is specified, no logo is shown in the footer for that item. The space however is still occupied. There should be default logo, such as for example the globe, for unknown labels. I am, however, unsure as to how to check whether a logo exists in Handlebars or whether that even is possible.~~ I've fixed this. However, it has to be ensured that the default social icon always comes before the other social icons in the style. A comment in the code about that has been added.

    • ~~When a lot of logos are specified, resizing of the window results in weird behavior: When the window width gets smaller at some point there are more logos on one row than there were when the window width was higher. The CSS display properties have to be set correctly. I unfortunately don't know what the right values are.~~ I had to set the max-width of the footer content. Although the mentioned property still applies, I have improved the footer to show more icons on bigger screens per row.

  • 12

    Excerpts, image aspect ratio, and featured post on smartphone mode

    Hi,

    Thanks for the great template!

    1. Is it possible to display excerpts?
    2. Is it possible to change the aspect ratio of a publication cover?
    3. is it possible to change the aspect ratio of a feature image in a post?
    4. When a feature post exists, on smartphone, there is no gap between a publication cover image and the feature image of the featured post. Is it possible to put a gap there?

    Thank you!

  • 13

    Bump decode-uri-component from 0.2.0 to 0.2.2 in /src

    Bumps decode-uri-component from 0.2.0 to 0.2.2.

    Release notes

    Sourced from decode-uri-component's releases.

    v0.2.2

    • Prevent overwriting previously decoded tokens 980e0bf

    https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.1...v0.2.2

    v0.2.1

    • Switch to GitHub workflows 76abc93
    • Fix issue where decode throws - fixes #6 746ca5d
    • Update license (#1) 486d7e2
    • Tidelift tasks a650457
    • Meta tweaks 66e1c28

    https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.0...v0.2.1

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

  • 14

    Bump engine.io from 6.2.0 to 6.2.1 in /src

    Bumps engine.io from 6.2.0 to 6.2.1.

    Release notes

    Sourced from engine.io's releases.

    6.2.1

    :warning: This release contains an important security fix :warning:

    A malicious client could send a specially crafted HTTP request, triggering an uncaught exception and killing the Node.js process:

    Error: read ECONNRESET
        at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
    Emitted 'error' event on Socket instance at:
        at emitErrorNT (internal/streams/destroy.js:106:8)
        at emitErrorCloseNT (internal/streams/destroy.js:74:3)
        at processTicksAndRejections (internal/process/task_queues.js:80:21) {
      errno: -104,
      code: 'ECONNRESET',
      syscall: 'read'
    }
    

    Please upgrade as soon as possible.

    Bug Fixes

    • catch errors when destroying invalid upgrades (#658) (425e833)
    Changelog

    Sourced from engine.io's changelog.

    6.2.1 (2022-11-20)

    :warning: This release contains an important security fix :warning:

    A malicious client could send a specially crafted HTTP request, triggering an uncaught exception and killing the Node.js process:

    Error: read ECONNRESET
        at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
    Emitted 'error' event on Socket instance at:
        at emitErrorNT (internal/streams/destroy.js:106:8)
        at emitErrorCloseNT (internal/streams/destroy.js:74:3)
        at processTicksAndRejections (internal/process/task_queues.js:80:21) {
      errno: -104,
      code: 'ECONNRESET',
      syscall: 'read'
    }
    

    Please upgrade as soon as possible.

    Bug Fixes

    • catch errors when destroying invalid upgrades (#658) (425e833)

    3.6.0 (2022-06-06)

    Bug Fixes

    Features

    • decrease the default value of maxHttpBufferSize (58e274c)

    This change reduces the default value from 100 mb to a more sane 1 mb.

    This helps protect the server against denial of service attacks by malicious clients sending huge amounts of data.

    See also: https://github.com/advisories/GHSA-j4f2-536g-r55m

    • increase the default value of pingTimeout (f55a79a)
    Commits
    • 24b847b chore(release): 6.2.1
    • 425e833 fix: catch errors when destroying invalid upgrades (#658)
    • 99adb00 chore(deps): bump xmlhttprequest-ssl and engine.io-client in /examples/latenc...
    • d196f6a chore(deps): bump minimatch from 3.0.4 to 3.1.2 (#660)
    • 7c1270f chore(deps): bump nanoid from 3.1.25 to 3.3.1 (#659)
    • 535a01d ci: add Node.js 18 in the test matrix
    • 1b71a6f docs: remove "Vanilla JS" highlight from README (#656)
    • 917d1d2 refactor: replace deprecated String.prototype.substr() (#646)
    • 020801a chore: add changelog for version 3.6.0
    • ed1d6f9 test: make test script work on Windows (#643)
    • See full diff in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

  • 15

    Theme development permission denied

    Hey there, I'm trying to set up the docker dev environement using colima.

    When I run pnpm run docker-watch the browser window opens up and starts loading, but I get "permission denied" errors, like these:

    [DOCKER] ghost  | chown: changing ownership of '/var/lib/ghost/content/themes/liebling/src/sass/fonts/icomoon/icomoon.eot': Permission denied
    [DOCKER] ghost  | chown: changing ownership of '/var/lib/ghost/content/themes/liebling/src/sass/fonts/icomoon/icomoon.svg': Permission denied
    [DOCKER] ghost  | chown: changing ownership of '/var/lib/ghost/content/themes/liebling/src/sass/app.scss': Permission denied
    
    DOCKER] ghost exited with code 1
    [DOCKER] docker-compose up exited with code 0
    --> Sending SIGTERM to other processes..
    [WEBPACK] npm run watch exited with code 0
    

    Any idea what direction I should look to debug?

  • 16

    Bump loader-utils and resolve-url-loader in /src

    Bumps loader-utils to 2.0.4 and updates ancestor dependencies loader-utils, loader-utils and resolve-url-loader. These dependencies need to be updated together.

    Updates loader-utils from 2.0.2 to 2.0.4

    Release notes

    Sourced from loader-utils's releases.

    v2.0.4

    2.0.4 (2022-11-11)

    Bug Fixes

    v2.0.3

    2.0.3 (2022-10-20)

    Bug Fixes

    • security: prototype pollution exploit (#217) (a93cf6f)
    Changelog

    Sourced from loader-utils's changelog.

    2.0.4 (2022-11-11)

    Bug Fixes

    2.0.3 (2022-10-20)

    Bug Fixes

    • security: prototype pollution exploit (#217) (a93cf6f)
    Commits

    Updates loader-utils from 1.4.0 to 2.0.4

    Release notes

    Sourced from loader-utils's releases.

    v2.0.4

    2.0.4 (2022-11-11)

    Bug Fixes

    v2.0.3

    2.0.3 (2022-10-20)

    Bug Fixes

    • security: prototype pollution exploit (#217) (a93cf6f)
    Changelog

    Sourced from loader-utils's changelog.

    2.0.4 (2022-11-11)

    Bug Fixes

    2.0.3 (2022-10-20)

    Bug Fixes

    • security: prototype pollution exploit (#217) (a93cf6f)
    Commits

    Updates resolve-url-loader from 3.1.2 to 5.0.0

    Release notes

    Sourced from resolve-url-loader's releases.

    5.0.0

    Breaking changes

    • Require node>=12.
    • Support only webpack>=4.
    • Update to [email protected]^8.
    • Remove rework engine (which was deprecated in V4).

    Bugfixes

    • Fix log messages not correctly normalising absolute paths to posix style on Windows platform
    • Fixes to end-to-end tests and test framework.

    5.0.0-beta.1

    Breaking changes

    • Require node>=12.
    • Support only webpack>=4.
    • Update to [email protected]^8.
    • Remove rework engine (which was deprecated in V4).

    Bugfixes

    • Fix log messages not correctly normalising absolute paths to posix style on Windows platform
    • Fixes to end-to-end tests and test framework.

    5.0.0-alpha.1

    Breaking changes

    • Require node>=12.
    • Support only webpack>=4.
    • Update to [email protected]^8.
    • Remove rework engine (which was deprecated in V4).

    Bugfixes

    • Fix log messages not correctly normalising absolute paths to posix style on Windows platform

    4.0.0

    Features

    • Better resolution of the original source location - You can more successfully use url() in variables and mixins.
    • Dependencies now accept a wider range and explicit dependency on rework and rework-visit has been removed.

    Breaking Changes

    • The engine option is deprecated which means the old rework engine is deprecated.
    • The keepQuery behaviour is now the default, the keepQuery option has been removed.
    • The removeCR option defaults to true when executing on Windows OS.
    • The absolute option has been removed.
    • The join option has changed.

    Migrating

    See the changlog.

    ... (truncated)

    Changelog

    Sourced from resolve-url-loader's changelog.

    resolve-url-loader

    Version 5

    Features

    • Update postcss and completely remove rework parser.

    Breaking Changes

    Migrating

    Remove the engine option if you are using it.

    Version 4

    Features

    • Better resolution of the original source location - You can more successfully use url() in variables and mixins.
    • Dependencies now accept a wider range and explicit dependency on rework and rework-visit has been removed.

    Breaking Changes

    • The engine option is deprecated which means the old rework engine is deprecated.
    • The keepQuery behaviour is now the default, the keepQuery option has been removed.
    • The removeCR option defaults to true when executing on Windows OS.
    • The absolute option has been removed.
    • The join option has changed.

    Migrating

    Remove the engine option if you are using it - the default "postcss" engine is much more reliable. The "rework" engine will still work for now but will be removed in the next major version.

    Remove the keepQuery option if you are using it.

    Remove the absolute option, webpack should work fine without it. If you have a specific need to rebase url() then you should use a separate loader.

    If you use a custom join function then you will need to refactor it to the new API. Refer to the advanced usage documentation.

    If you wish to still use engine: "rework" then note that rework and rework-visit packages are now peerDependencies that must be explicitly installed by you.

    Version 3

    Features

    • Use postcss parser by default. This is long overdue as the old rework parser doesn't cope with modern css.

    ... (truncated)

    Commits
    • bf01da9 5.0.0
    • 78393f6 update branch references to v5
    • 6787839 github actions for CI
    • 1457038 update changelog and readme
    • a01faf9 5.0.0-beta.1
    • fb09fae remove the engine option harder, ensure deprecation warning is tested
    • 5654fa4 remove the engine option and related tests, use getOptions from loader where ...
    • 10f9cdb 5.0.0-alpha.1
    • b168dd3 adjust deprecation message for engine option
    • 29e142a normalise windows absolute paths to posix format in log messages
    • Additional commits viewable in compare view

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

  • 17

    Remove Social Media Buttons

    Hi. I need to hide the social media buttons from my website for now. They are removed from the footer on the homepage, but they still show up in all posts in the top right. I found this for twiter:

    I am still missing to hide Facebook, which I tried to replace the web address in the code before, but it doesn't work.

    Thanks in advance. Regards.