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:
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…
Rollback to 8.6 RC its working so the problem must be from RC to final
If you manage multiple themes with similar npm dependencies you should install npm packages globally and link them in your theme directories. First of all this saves a lot of disk space. But it also disburdens the upgrade process of development frameworks and toolkits that are used across projects.
1. Install packages globally by adding the “-g” flag: $ npm install -g package_1 package_2 package_3 package_4 etc.
2. Link the packages in your local theme directory/directories:
Bootstrap-Theme $ npm link bootstrap @popperjs/core ...
Material-Theme $ npm link material-components-web ...
FSE-Theme $ npm link autoprefixer css-loader sass sass-loader ...
Our latest WordPress Plugin Directory addition integrates the awesome Bootstrap Icons (MIT) library in the WordPress rich-text toolbar without requiring any coding experience. Just the way it should be.
1300+ pixel perfect webfont icons
Small filesize
Easy WYSIWYG integration: No Shortcodes!
Privacy by design: No CDN hosted files!
Autofilter
You can download it from the WordPress Plugin Directory:
A working and maintained Emoji Picker Plugin has been brought back to WordPress. Easily add Emojis from any rich-text block like Paragraphs, Headings, Lists, etc. without leaving the Editor.
Emojis are pictograms used in instant messengers, forums and web pages to reflect emotions. They have become so popular that Oxford Dictionaries has named “😂” word of the year 2015.
Nowadays all browsers and operating systems support the Emoji characters. When picking your Emojis from the Emoji Toolbar they will be added in raw format so no images are loaded on the frontend.
Block based Themes are coming to WordPress sooner or later and we just published the first “beta” release of our Full Site Editing Starter Theme.
If you see yourself as an early adopter who likes to get his/her hands dirty feel free to generate a copy via the Theme Generator: https://them.es/starter-fse
The source code is licensed under GPLv2 and has been published on GitHub.
Full Site Editing is a collection of features that allow to fully customize a WordPress site via a new site editor. Overall the Full Site Editing experience using block based Themes looks promising and already works pretty well but you need to be aware that not all features are final and that bugs will appear during development.
Now a 100% (!) PageSpeed score is achievable with WordPress. Even on Mobile.
At the current state (WordPress version <5.9) this Starter Theme is not recommended for production sites. Please use it at your own risk and provide technical feedback to the Gutenberg team if possible!
One more thing: Block based features are still in development and have not yet been fully integrated in WordPress core. In order to enable the Site editor you need to install the Gutenberg Plugin on your site.
Update: In the meantime WordPress supports Block themes in Core and it’s safe to develop websites using the FSE Starter Theme.
it’s hard to reproduce what’s wrong with your setup without seeing the full SCSS source.
Could you first make sure that /assets/css/main.css is writable or delete main.css and try to recompile it.
If it’s still failing would it be possible to share your main.scss by creating a ZIP file and dragging it in the Uploader (see Sidebar)?
one more question. I want to modify the main blog page loop… where is index.php calling the loop from? I see the single page loop, but not the one which lists the blog posts.
The post loop in the archive templates (i.e. index, author, category, etc.) is called via get_template_part( 'archive', 'loop' ) which loads the general archive-loop.php template. There you can see that the content-index.php template is referenced.
I can edit main.scss, watch runs and it all works, except options.
I change color vars – $red: for example, i change breakpoints, $grid-breakpoints, but no any change i see in the theme.
The Gulp watch task should work out of the box. Could you make sure that you have read+write access to /assets/css/main.css. You could also try to delete the main.css file and recompile it from the SASS source.
Well, i’m not saying, that gulp is not working. It does it’s job!
The bug is that i can’t change these global vars, like breakpoints and colors. I can successfully create my own ones, and it works (as i already did for the colors), and thank G-d, i do not really need to change breakpoints in this project, but as for the future…
But I guess you already know that. So please double check that you are adding these variables in your main.scss file before any @import “../node_modules/bootstrap/scss/bootstrap”; statements.
This has been tested locally by us and confirmed to be working. If you still don’t manage to change the grid breakpoints, would it be possible to share your main.scss file? You can use the uploader in the sidebar to share it as a ZIP file.
I’m confused as Gulp only seems to recognize main.scss and changing any files in node_modules/bootstrap/scss aren’t recognized. I can make changes in node_modules/bootstrap/scss but then I have to change something in main.scss to get Gulp to compile. This seems to be an incredibly slow way to develop. Am I missing a path in my gulpfile.js? Or am I supposed to run npm install in node_modules/bootstrap/ ?
Over the last couple of months we’ve been working hard on the latest addition to our product line – a complete billing suite which integrates seamlessly into WordPress – and we’re happy to announce that the free version got approved and has been shipped to the WordPress Plugin directory.
🙌🏻 🙌🏻 🙌🏻
If you are working as a Freelancer or are responsible for Accounting and Billing in a small agency and are looking for an easy-to-use, future-proof PbD* solution to create Invoices, Quotes and basic Accounting records, go on and give Billy a try.
*Privacy by Design: Billy posts are privately published, by default.
The plugin will work with any modern WordPress theme that supports the Block editor.
Your valuable comments and suggestions are highly appreciated and will be examined by real people. Promised.
In the meantime we are getting the PRO add-on ready which will soon be is available for purchase here: https://them.es/plugins/billy
Billy Pro has some really cool extra features and integrates CRM tools which may speed up your billing processes rapidly.
Contact management
Address book
Upcoming Birthdays widget for your contacts
Enhanced Invoices, Quotes and Accounting
Stats & charts
GDPR compliant by implementing the WordPress Personal Data Exporter
…and much more
Since the “Pro” version will be available as an add-on, installing the free Plugin from the WordPress directory is required in any case – so nothing is ever lost by checking Billy “Free” out.
I’ve been investigating your theme and like the simplicity and that it already includes basics such as the Bootstrap menu walker that designers like myself don’t really want to build.
I’m coming from using FoundationPress for number of years which did not facilitate child themes.
Somewhere on your site I saw a note on regarding child themes and build tools. I’m not finding it now. I want to set a child theme and use sass. I’m not clear how to do this with them.es and I haven’t set a child theme in a sass environment. So, looking for some reference for this.
Creating a child theme for one of the Starter Themes is not required and not recommended. According to the official WordPress docs a Child Theme allows you to change small aspects of your site’s appearance yet still preserve your theme’s look and functionality.
The purpose of a Starter theme is to start developing from scratch with a small code base and not to use it as a Parent Theme.
If you want to build a new them.es Starter Theme you need to be familiar with npm development in order to setup the required frontend build tools.
The following resource should help you setup your DEV environment: https://them.es/starter-bootstrap/getting-started
Update: The following GitHub thread may be helpful for anyone experiencing this issue with Local https://github.com/them-es/starter-bootstrap/issues/31