It's 3 am and I'm hitting the sack. BSThemes V1.0.1 for non-techies has been launched. Enjoy :-)
NOTE; Still more work to be done...support, connection to newsletter, etc.
(13 posts) (4 voices)
Thank you Tim!!
You are most welcome Matt :-)
V1.0.1 Release Note:
V1.0.1 is the initial Release Candidate (RC) of BackStop Themes.
Establish a stable release of BackStop Themes as an open source fork of the MySiteMyWay themes AND release a publicly available repository and download area for these themes.
This is the first step in the BackStop Themes roadmap which will be made available for public comment over the next month.
- Bugfix: Remove function mysite_texturize_shortcode_before to work with Events-Manager plug-in (NOTE: Adding newline ahead of BST shortcodes now manual process)
- Bugfix: Replace http:// with // or nothing (so themes work with SSL and non-ssl implementations)
- Bugfix: Correct WordPress warnings & errors up to and including WP4.6.1
- Bugfix: Correct PHP warnings & errors up to and including PHP7
- Enhancment: Add theme option metaboxes to custom posts
- Enhancment: Replaced gzencoded compressed default options with expanded options for traceability and to pass theme security checks
RC (Release Candidate)
Assessment: Only minor changes were made to the MSMW source-code fork to minimise the risk of impacting established sites but there are further maintenance tasks to complete before I consider this a formal LTS (Long Term Support) release.
- The jQuery used is old.
- Most of the shortcodes are based on older versions of open source packages that should be updated to the latest versions.
- Testing for WP4.7 has not yet commenced
- Establish Trouble Ticket / support for non-techies (techies can submit an issue via the GitLab repository.
thank you very much.
Do you think that it is recommendable to download Backstop-Dejavu v1.0.1 and upgrade MSMW-Dejavu v2.8 (with a fixed slider issue) which I run currently on my site?
Backstop-DejaVu v1.0.1 is MSMWv2.8 with PHP and WP warnings and errors fixed up to WP4.6.1 and PHP7.
The modifications I made were small in number and previously tested so I would expect the BST version is a better option than the MSMW version. You should use all normal cautions if possible...test on staging site, backup before upgrade, etc.
Keep in mind that even the improved BST versions need more work before I would be content. Testing for WP4.7 won't be completed until next week. There are also jQuery warnings & errors that I will move to fixing next.
WordPress 4.7 update for BSThemesV1.0.1
I have just updated the https://backstopthemes.com site to WP4.7 and the nine BackStop Themes sub-sites. Each sub-site corresponds to a BackStop theme that is a fork of a previous MSMW theme with the PHP and WordPress warnings & errors corrected.
Result: No new php or WordPress warnings or errors generated (which is good :-).
Preliminary testing of the various BSThemesV1.0.1 shows all basic front-end and admin functionality works fine. Further in-depth testing will be completed over the next few weeks for those who are not in a rush to upgrade to WP4.7 and are happy to wait for further testing results.
Current Issues of Note:
Only issues of note so far are:
1) Momentary admin white screen of death immediately on updating to WP4.7. Don't panic...just wait a minute and refresh the admin page and all is fine. This is no a theme error. This is a WordPress / PHP error that has been raised with the WP core devs (see https://core.trac.wordpress.org/ticket/39135).
2) BackStop / MSMW themes Skin generator works for skin switching but you get an infinite waiting icon if you attempt to create a new skin or manage skins. This is likely related to MSMW using a 2-year old jQuery version. BSThemes has a plan to clean up the jQuery warnings, errors & core conflicts over the next few weeks.
Stay tuned...more to come...
thanks a lot! You are great!
You are most welcome Tom :-)
I am hoping to get a v1.0.2 out 23 Jan 2017 with the following enhancements:
- jQuery version review and update
- A clean pass from WordPress ThemeCheck plug-in
- Enhancement to support auto theme update via admin from GitLab or AWS (since BSThemes are not in the WordPress theme repository...yet)
You can keep an eye on the project milestones at the following location:
Have a great Christmas break :-)
Thanks so much for your work on this. The MSMW project was most excellent and their themes among the best and easiest to work with I have ever found. So its demise was a blow for those of us who have invested in it for our projects. To keep it going is brilliant, and I cannot thank you enough.
You are most welcome.
I am about to post a caution to the non-techies that upgrading from a MSMW theme to a bst-theme is not the point & click process I would have hoped. Since it is recognised as a new theme the previous theme configuration needs to be copied across (theme configuration including custom css and javscript AND widgets).
Additionally, there appears to be a glitch in the default data initialisation. This bug may have always been there but I have never switched a website from one MSMW theme to another. The new theme may overwrite a previously configured widget in the database.
Stay tuned for an update. It will probably take me a week AND its Christmas time so it may not be fully repaired and updated until after Christmas.
Sorry everyone. I'm fixing the legacy MSMW bugs as fast as I can.
thanks for the warning. So I´ll wait then till we hear more from you.
Merry Christmas to you Tom :-)
PS: For those that did not read the other blog post on this topic...
I think the root cause of the upgrade quirk is that this process is neither the upgrade of a theme (BST theme uses different underlying theme naming than MSMW for legal reasons) or the switch of one theme for another (the BST them and MSMW theme are virtually identical technically...with bug fixes of course).
So I think the issue is that the themes have different database tables (a WordPress theme convention) but share common database search & update naming.
I knew when I create BSThemes that a global renaming would be the safest course but I didn't want to break anyone's custom code or css.
I'll sort it out though. I believe this is an isolated issue related to the loading of sample content on installation. I am pretty sure I just need to add a pre-check for existing content to get around that.
Stay tuned :-)
You must log in to post.