If you noticed, I started to customize the great plugin by lonalore with the name Metatag. This plugin is so useful that I had asked a long time ago to add those features to the core. Now I am glad they didn't do it; otherwise, I wouldn't be able to customize it.
Why I customized it? This plugin is for very advanced users. It's not easy to understand how it works. I had a vague idea of what results should be, and when I hit different outputs, I was lost. I need to be sure it works the way it should work before I fully add my solution for canonicals and double content.
Now I finished the first step. To get plugin more understandable and be able to check its results.
So what version 2.2 do?
Option to set needed metatags and hide not used ones (some details and help need to be fixed)
Added numbering to have correct (logical) order for default settings and supported entities.
Added support for contact, login, signup and forgot password pages (mainly because of robots metatags). This solution solves double content for those pages.
Possibility to update addon list (normally you can do it only with install/uninstall plugin)
Displaying data value for quick visual checks.
Added display of available single entity token (new tokens added and next ones will be added)
Download Metatag Tab available with JM Download plugin
All metatag widgets now display real values what should be on entity page
Now it's time to check all tokens and add a new token for canonical URLs.
I work on 2 big "projects". The first one is porting efiction script for e107. That script is new for me, so at first, I need to get how it works. It's a lot of work and only in my free time. The second one is new theme based on this HTML template. It means new plugins or improving existing ones. For example teammembers and testimonials.
efiction blocks system (better than my old UNNuke version)
Testimonials [tested with e107 2.3 and PHP 7.2 + 7.3]
It is the customized testimonial plugin by lonalore. You can find code with demo data and example for theme in my github repository. For now, it is only an example of what can be possible.
The idea is from the efiction author's module (author profile, author fields, author custom fields). But I am short of time to finish it, so I decided to do new plugin.
New theme Hestia released. Inspired and fully compatible with Gaia. Free for users with Gaia licence. We tested it with the latest versions of JM Theme and Elements plugins.
This is Dark version of Gaia released under the name Hestia, because it's not only about colours.
- the theme is free for the users with Gaia Full Pack licence, just ask for it. Thanks for your support.
- if you have plugins licences, price is 10 Eur (users with OpenMind class). Thanks for your support.
- otherwise, you need to get the full pack
From this point, there is possible to have the developer version of this theme: Bootstrap 3 in sass version, e107 stuff in sass version and Hestia itself sass version together. Developer licence of HTML Gaia now costs $119, so the price of e107 version is the same. We are trying to have one sass version for Gaia and Hestia, but Hestia is on a higher level.
Fixed parallax effect on Chrome browser (on mobiles it's blocked) - it's not solved in the original HTML theme
Fixed some of HTML markup issues vs W3C validation in original HTML layout - they don't fix this in the HTML theme
Fixed navbar collapse breakpoint (moved from small to the middle). The real e107 site has more than few links in the navigation, Gaia uses not the standard solution for the mobile sidebar, so we have to fix this for e107
fixed header look for mobile devices in landscape position - they missed this in HTML version
unified primary and danger colours (sometimes they used gold colour instead of primary/danger)
added Style Guide for testing output e107 core not covered original HTML source
added Media Query Test to be able to check all elements on most used devices online
To fix original HTML css, we completely rewrote way how css is built.
From this point, there is possible to have the developer version of this theme: Bootstrap 3 in sass version, e107 stuff in sass version and Gaia itself sass version together. Developer licence of HTML Gaia now costs $119, so the price of e107 version is the same.
Added easier way for the update with older themes - supported now old themes too (at least in layout option folder)
Version 2.1.5 solves the problem with menu manager in git version 2.2.2. The problem was that the new core version will use layouts folder for HTML layouts and if this folder exists, new layout's way is detected. This problem is not there with version 2.2.1.
We rewrote Gaia theme to use jmlayouts folder, but for older installation, we added a test where to look for layout's settings (jmlayouts or layouts).
What are the scenarios with Gaia Pack 2.0.0:
The theme is already used (f.e. customized): download JMT 2.1, check update instruction here and update only the plugin. The only necessary thing is to copy options files from layouts folder to jmtheme folder. If anything fails, only resave your layouts. No changes in the theme itself are needed!
It's a new installation: install full pack and then update JMT plugin (if you don't do it this way, you will need to set your layouts manually). Don't forget to move options files.
You have already JMT 2.1 installed: install Gaia, move options files. You will need to set your headers/footers manually.
Wait for Gaia 2.1.0 with fix folder structure and changed demo install data for layouts.
What are the differences:
2.1.1 removed field description
2.1.1 removed field image preview
2.1.1 added fields header and footer (in JMT 2.0 they are part of options)
2.1.1 new file names for HTML layout use underscore (header_, footer_), file names for PHP layout use hyphens (header-, footer-)
2.1.3 layouts folder is now standard folder for e107 2.2.2,
2.1.4 change options in layouts folder can be possible for 2.2.1 themes., no need to move options files to jmtheme folder
2.1.4 new added backwards compatibility - themes without theme.html will look options inside layouts folder as before, themes with theme.html will look in jmtheme folder
2.1.5 change added test for loading layout settings - if layouts folder exists, it looks there, if jmlayouts folder exists, it loads from this folder.
What is new:
the different screen of layouts
2.1.1 added the possibility to generate layouts (no need for manual adding or demo data)
2.1.1 added single shortcodes for custom header and footer available to use in both e107 versions
2.1.1 added option to delete all not used menus with one click