Welcome! This Forum is our main place to share official announcements and to help you get support for them.es products. If you have general inquiries on WordPress or need assistance with theme customizations, please head over to the following sites, maintained by the awesome WordPress Community:
/ emoji-toolbarGreat Plugin with Smooth Integration
⭐️⭐️⭐️⭐️⭐️
No country flags
⭐️⭐️⭐️⭐️⭐️
Wow – works great! Plug & play!
⭐️⭐️⭐️⭐️⭐️
/ i-dont-like-spamWorks flawlessly with WPForms
⭐️⭐️⭐️⭐️⭐️
no more NINJA FORMS canada pharmacy spam emails!!!!!
⭐️⭐️⭐️⭐️⭐️
Update: The following GitHub thread may be helpful for anyone experiencing this issue with Local https://github.com/them-es/starter-bootstrap/issues/31
Hi @kmeronuk, this is a known issue (at least on some environments) and has been reported by other users as…
Hi thanks for the hint, after update to 8.61 its working again. I was think its a problem with your…
Hi stefanbd, thanks for getting in touch. You’re right – there seems to be a bug in WooCommerce v8.6.0 (see…
anniversary Billy blocks boilerplate bootstrap countup development full site editing GitHub gutenberg headless-cms jquery JS lts material design npm plugin plus polymer reactjs sass starter support them.es+ theme tutorial VanillaJS webpack wordpress wp-api WP20
I’ve integrated the theme as instructed, but I’m getting these errors in the console. It doesn’t appear to be affecting the “watch” script as changes are taking place, but any thoughts on how I can fix this to keep it from flooding my console? I’m not too familiar w/ WebPack. Any direction is most appreciated. Thanks.
Thanks for the detailed information including relevant screenshots.
A similar issue has never been reported and it seems to be related to the webpack DevServer config. Here you can find all possible configuration settings: https://webpack.js.org/configuration/dev-server/
To fix it, I would start tinkering with the one’s related to “WebSocket”.
Maybe explicitly defining webSocketTransport ws works (https://webpack.js.org/configuration/dev-server/#websockettransport):
/ client: {
webSocketTransport: 'ws',
},
webSocketServer: 'ws',Alternatively you could try defining your webSocketURL (https://webpack.js.org/configuration/dev-server/#websocketurl):
client: {
webSocketURL: '{ADD YOUR LOCAL WS URL HERE}',
},Maybe unrelated, but I noticed that you’re using a wss:// protocol (= WebSocket SSL connection) which is unusual on localhost systems as you’d have to provide a valid SSL certificate.
Please let me know if any of this helped.
I’ve tried different combinations of the config settings, as well as your above recommendations without success.
You may be on to something regarding the SSL certificate. When inspecting in Safari, the console expresses an “An SSL error has occurred and a secure connections to the server cannot be made.” regarding the WebSocket connection – while in Chrome, it just says the connection failed seen in the OG screenshots.
I spun up another host following your instructions in case I missed anything:
Uploaded and activated the new theme in WordPress
“npm install” in the console
“npm run watch” to start webpack
The instance uses wss:// protocol to begin with without me changing anything. Is there a way to start using just the ws:// protocol and potentially avoiding that error?
I’m using MAMP Pro to spin up the WordPress instance, which installs an SSL certificate for the site, but not sure that has anything to do with the WebSocket SSL.
When disabling the SSL certificate for WordPress, the WebSocket errors resolve, but then I get I get “[webpack-dev-server] Invalid Host/Origin header” errors in both browsers.
According to Google webpack-dev-server invalid host/origin header the following resources may be helpful:
https://webpack.js.org/configuration/dev-server/#devserverallowedhosts
https://stackoverflow.com/questions/53906803/webpack-4-hot-reload-invalid-host-origin-header
https://stackoverflow.com/questions/69246770/webpack-5-disablehostcheck
https://github.com/webpack/webpack-dev-server/issues/1604
I’ve implemented the allowedHosts option and targeted my local.mopqc host, which removes the Invalid Host/Origin error, but now causes an infinite “App Updated. reloading…” loop. I haven’t found a solution when combing the web, so at this point I’m keen to just ignore it or switch starter themes altogether. I appreciate your help regardless, but this remains unresolved.
Sorry about that and good luck anyway.
Maybe the MAMP support team https://www.mamp.info/en/mamp-pro/support/ has experience in setting up a working webpack-dev-server config?
Otherwise you’d have to consult a webpack expert who could help you fix the infinite reloading issue. One last try: Try to add your IP address, incl./excl. the port, instead of your local URL (in your case probably via the webSocketURL configuration), as stated here: https://github.com/webpack/webpack-dev-server/issues/4232#issuecomment-1588507348
Your Bootstrap theme, simple and straightforward, used to work like a charm. Now it’s a pain in the **s to install and configure, it’s clunky as hell and takes hours to debug in VScode and Flywheel. Why guys?!
We’re always open to constructive feedback – even if it’s negative – but without further details your complaint can’t be taken seriously.
So many questions 🤨
theme is the latest Bootstrap theme available on your site
MacOS Sonoma, Flywheel local Version 8.1.0+6514, PHP 8, Apache, MySQL 8.0.16, npm 10.2.4, webpack 5.89.0
Wordpress 6.4.1
No plugin yet, project is blank
Our main problem is it worked well… with Gulp. It’s much more complicated to have it work between flywheel & webpack, the whole process is quite confusing to say the least
Well, we don’t force you to use the new webpack config which, by the way, is much leaner and at the same time more future proof because it makes use of a WordPress internal configuration file.
Feel free to implement the old Gulp setup if it better suits your specific needs.
Here you can download the legacy Gulpfile: https://github.com/them-es/themes-starter-bootstrap/blob/24ac88a2738eaeeaf49b42a1d6ce28bb8601fd8d/gulpfile.js
And here is the legacy webpack config: https://github.com/them-es/themes-starter-bootstrap/blob/3b2b6db5b26337f68b795c2c2c0dd152ccdd6987/webpack.config.js
The weird thing is that webpack already has been implemented in the past for bundling the JS files. And webpack or any frontend assets are completely independent from the server setup (i.e. Local “Flywheel”).
You could play around with the webpack config and for instance change the mode setting to "development". This should speed up compile time but you would have to rebuild the assets for production before deploying them live.
Probably there is always room for improvements in the current webpack configuration. Pull requests are welcome!
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!
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
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+).
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.
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.
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
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
We’ve received feedback from our community that the now retired 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 SASS-CSS compilation and JS-bundling…
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 new build workflow worked pretty well and that’s why we decided to roll it out to all our Starter Themes (Full Site Editing, Bootstrap and Material Design) and include this new setup exclusively, meaning that Gulp (including its internal dependencies) is not needed anymore.
Start the development process:
$ npm run watch
Build and minify the assets:
$ npm run build
👆 Breaking change: Theme 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. On the other hand, if you want to keep the old workflow, feel free to keep it as long as it works on your side.
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:
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
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.
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!
Great, thanks!
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.
Today we’ve published Billy Pro v1.4.1. This follow-up release allows you to add due dates to To do checklists and…