• Lightbox for Bootstrap 5

    I was using Ekko Lightbox with the Bootstrap 4* theme, but since updating to Bootstrap 5 it is no longer supported.

    I’ve tried using the Lightbox for Bootstrap 5, but I can’t seem to get it to work. I tried on a clean them install with no other plug ins and still nada….

    Installed using npm i bs5-lightbox and import ‘bs5-lightbox’; as per the instructions on this page:
    https://trvswgnr.github.io/bs5-lightbox/

    Thanks in advance for any clues!


    Comments
    1
    1. them.es Avatar

      Hi leebaz,
      sorry to read that you’re having trouble with your site but please understand that we can’t provide support for third-party tools.
      You could ask for help in the Github repo you referred to: https://github.com/trvswgnr/bs5-lightbox/issues
      As an alternative solution there are several ready-to-use Lightbox plugins in the WordPress Plugins directory which may be worth a try: https://wordpress.org/plugins/search/lightbox

    Leave a Reply

  • New Forum 🎉

    We’re happy to announce that our Support Forum has been relaunched with a custom-built Theme based on our FSE Starter Block Theme (OpenSource, GPL2+).

    Why the change?

    When them.es/Support went live in 2015, we decided to set it up with the (now deprecated) P2 “Breathe” Theme and its companion, the o2 Plugin.

    All in all it worked very well for years and we even managed to extend it according to our needs by using a Child theme. But recently the efforts to ensure compatibility with the latest WordPress and PHP versions have become quite a burden. Monkey patches 🙈 had to be applied to work around issues — and this is bad practice for obvious reasons.

    Also, relying on code that is not maintained anymore was a no-go.

    While evaluating existing Forum plugins and similar solutions it soon turned out that they all lack important features and could not be customized in a way that was satisfying. Putting the code base again in a dependence on third-party software with an unclear future was another no-go.

    So we decided to go all-in and to develop our own tailored Support Theme. Thanks to the Gutenberg plugin and its new Interactivity API which currently is in active development, all requirements could be fulfilled without compromise.

    What changed?

    From a user-perspective not much changed at all, as all previous features like Search autocomplete, Frontend posting, File uploading and Marking requests as resolved, have been incorporated.

    Besides the new foundation which reduced the code footprint to an absolute minimum, we polished the design a bit and added a better UX with interactive elements.

    Furthermore users now can format their posts with basic Markdown syntax, if needed.

    As a nice side effect the overall page loading performance has improved a lot.

    Of course a re-release that makes use of a newish approach with bleeding-edge features may contain bugs and we kindly ask everyone to consider this site “Beta” for the time being. It’s quite possible that things get out of order or even break.

    If you notice some hiccups or errors, please let us know, by commenting below, so that we can fix it. And if you miss something essential, we always keep the door open for feature-requests. Please mention why you are requesting it and what problem it may solve.

    Hopefully you like the new Support Forum as much as we do.


    Comments
    0

    Leave a Reply

  • Hi, i have error on…

    Hi, i have error on my console and I have error in my terminal when I run npm run watch
    “WARNING in asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
    This can impact web performance.
    Assets:
    main.css (284 KiB)

    WARNING in entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
    Entrypoints:
    main (484 KiB)
    main.css
    main.js
    main.asset.php

    WARNING in webpack performance recommendations:
    You can limit the size of your bundles by using import() or require.ensure to lazy load some parts of your application.
    For more info visit https://webpack.js.org/guides/code-splitting/

    How to solve this error


    Comments
    1
    1. them.es Avatar

      This warning doesn’t produce an error and can be considered a recommendation. If you want to reduce the file size you can try to deactivate unneeded modules in main.scss (https://github.com/them-es/themes-starter-bootstrap/blob/main/assets/main.scss#L78-L112) but if this is not possible you can hide the warning via your webpack config: See https://stackoverflow.com/a/41167614 and https://github.com/webpack/webpack/issues/3486

    Leave a Reply

  • Starter Themes with a new build workflow

    We’ve received feedback from our community that the old build workflow (using Gulp and/or webpack to generate the CSS/JS assets) included several package vulnerabilities that have not been fixed for quite a while and obviously have become unmaintained by the creators.

    One could argue that this should not be problematic, as these dependencies only affect the local development system – and as long as the build process still works, there’s no need to change a running system.
    But using obsolete and unsupported software can be dangerous and can break things “overnight”. Not to mention potential security risks that may arise in the web development stack.

    So it was necessary to find a new simple, modern and future-proof build process for the frontend assets
    Fortunately the research did not take too long. The @wordpress/scripts package from the awesome Gutenberg community already comes with a proven and tested webpack configuration specific to WordPress development, which made it a perfect candidate to try out.

    After some trial-and-error the build process worked pretty well and that’s why all our Starter Themes (Full Site Editing, Bootstrap and Material Design) have been updated to include this “webpack only” workflow from WordPress. From now on Gulp (including its several internal dependencies that are outdated) is not needed anymore.

    Start the development process:
    $ npm run watch
    Build and minify the assets:
    $ npm run build

    👆 Breaking change: The build directories have been moved from /assets/css and /assets/js to /build which aligns with the @wordpress configuration. If you want to include the new workflow in an existing theme, please have a look at the source code in the Github repositories of the Starter Theme and adjust the paths of the JS/CSS assets in functions.php accordingly.


    Comments
    0

    Leave a Reply

  • WordPress Playground

    Would you like to play around with an instant WordPress installation that runs in your browser?

    Visit https://them.es/playground [🪄 powered by playground.wordpress.net] and give it a try.

    Quickly demonstrate the WordPress dashboard to interested people or temporarily test Themes and Plugins without the need of an entire web server:


    Comments
    0

    Leave a Reply

  • 20 years WordPress

    Today our favorite CMS celebrates its 20th anniversary 🎉. A special website dedicated to this event has been established by the WordPress team:

    What started as a way to make a better blogging experience has grown into a vibrant open source project that powers an ever-growing percentage of the world’s websites.

    https://wp20.wordpress.net

    Let’s commemorate some historic milestones, the WordPress project passed within two decades:

    May 2003: WordPress 0.7 – The first release

    January 2004: WordPress 1.0

    May 2004: Support for plugins

    August 2006: The first WordCamp has been organized

    December 2008: Automatic upgrades with a single click

    June 2010: Multisite functionality

    October 2013: Automatic maintenance and security background updates

    December 2015: The WP-API has been integrated

    December 2018: A new block-based Editor

    July 2021: theme.json

    January 2022: Full Site Editing


    Comments
    0

    Leave a Reply

  • Hi, I’ve installed everything for…

    Unresolved Resolved

    Hi, I’ve installed everything for the bootstrap theme and trying to follow the instructions here: https://them.es/setup/
    Where it says “import the provided XML”, where is this provided? I can’t find it anywhere.


    Comments
    2
    1. them.es Avatar

      You’re right. The demo content XML is not shipped with the themes anymore. But you can download the file from the following resource instead: https://codex.wordpress.org/Theme_Unit_Test
      The Setup guide has been updated!

    Leave a Reply

  • Hi,

    Unresolved Resolved

    When my site is loading, this link https://tl.ytlogs.ru/timesince is running in the background.
    I use this start theme for two my projects, now i have problems.


    Comments
    0

    Leave a Reply

  • I have been trying to…

    I have been trying to edit the website, from the given questionaire but, i do not have any option to change the contents of the website


    Comments
    0

    Leave a Reply

  • I get this /#more-57 in…

    I get this /#more-57 in my url from archive page on read-more link. SO how can I get rid of it?
    Tnx


    Comments
    2
    1. pinky08 Avatar

      He assumes that it is a post id

    2. them.es Avatar

      Not sure if this is the right place for this kind of support question as it’s not possible to replicate the issue without more information. Internal links (i.e. # page jumps) like you describe are not included in any of the Starter Themes we maintain. Probably WP stackexchange would be a better platform to ask for help.

    Leave a Reply