I bit the bullet today and upgraded an inFocus site running v3.9 to WP 4.7 and all seems to work OK. :-)
Wordpress 4.7 seems OK
(13 posts) (5 voices)
Thank you so much for confirming!
Thanks for the heads up. Always my first thought to come here when I see a Wordpress update is out and see what has broken this time.
Got two sites on these themes yet and just haven't had time to migrate them. Not big sites... just not enough time to strip out all the MSMY framework from pages...
I have fixed WP and PHP warnings and errors up to 4.6.1 and a couple of bugs that have been around for a few years. I'll test 4.7 and adjust as necessary over the coming week. Over the next month I will progressively update the theme components to their latest levels and phase out TimThumb.
NOTE: This does not cover inFocus or Awake which are proprietary Themeforest / WebTreats themes.
Your endeavor looks good OnePressTech - good luck!
Unfortunately I was a pretty early adopter and the only two sites I have left on the MSMY framework is actually an inFocus site and an Awake site...
Just to update, I upgraded to Wordpress 4.7 after Ian's post and it works fine.
Interesting for those of you who've upgraded to 4.7 — while things may look okay, have you dug into the backend?
Things broken for me:
1) Shortcode generator doesn't work on pages etc.
2) Cannot switch between Text/Visual in WP text editor
3) Unable to edit "SKINS"
I did the update and had manually fixed the PHP issue with the brackets, other than that I've made no other changes to the theme files.
Has anyone else experienced this?
@OnePressTech good luck, I did notice your Construct theme and others on the non-technie page, perhaps I should move to your updated theme files? Thanks so much for your endeavor — very cool and admirable
I have experienced these bugs and expect they are jQuery issues / conflicts. I have been experiencing your bug #2 since 4.6.1 on PHP5.4.
I have scheduled to analyse / fix jQuery issues in the V1.0.2 version of BackStop Themes due to be released in January.
NOTE: Regarding switch from MSMW-->BackStop Theme V1.0.1...I recommend caution. I found a glitch in the MSMW --> BackStop theme replacement process that may muck up the contents of the last widget in the widget list. Ensure you have a backup and can restore it if you have switch-over issues. I'll be looking to fix that in the V1.0.2 release after Christmas. The widget overwrite glitch only occurs if you load and enable a backstop theme then switch back to the previous MSMW theme.
Thank you @OnePressTech for the info—So since I posted, I did try to switch to the BackStop 1.0.1 and did have some behavior issues related primarily to the home page layout, and of course, custom skins that aren't in the styles currently.
I'll keep my eye out for the widget issue, but so far this is on a staging dev server so it's isolated from the live site. So still checking it out.
The issue with #2 above is fixed with BS-Construct 1.0.1 — as far as I have tested.
Thank you so much for your efforts and interest in these MSMW themes; I'll certainly look for the 1.0.2 in January and keep you posted via this thread of any other discoveries.
Thanks heaps @MacMyDay. I like your community spirit. Cheers for the feedback on your upgrade experiences :-)
The migration from MSMW to BackStop themes will be an incremental process. What I don't want to do is bite off more than is reasonable to chew and end up with a theme of uncertain quality. With the exception of the theme migration glitch which I will now focus some energy on sorting out, changes I make should always improve the quality. All changes will be clearly auditable in the GitLab repository with each repository commit solving a specific problem or problem category.
Skins audit is on my 1.0.2 list...thanks for the reminder...I forgot to put it in the GitLab milestone (corrected now).
Question: Regarding your BST-theme upgrade experience related to home page layout...can you clarify the behaviour issues related to home page layout so I can look out for it in my testing?
Question 2: What process did you follow to do the BSTheme upgrade (e.g. load new theme, make it active, manually update the theme configuration and widget data...which of course...is theme-specific)?
@MacMyDay - just re-tried all the issues you document as broken with 4.7 and I do not have any of those issues with inFocus, they all work as they should.
Sorry for the delay, I don't get notice on these new responses, so bear with me!
Regarding the home page—it appeared when I made the switch the slider didn't work ( i think images location break) and the background, color scheme and other items related to the skin (CSS) that I'd modified didn't take. It looked like a totally different website form color and background.
All I did was to use the Appearance tool in WP and change theme to BST-Construct — Did not dig into the widget data, but it appears that on home page the sidebar (which would be a widget issue) doesn't show any content.
Have you done more work and should I test again? Also, since I've done the swap to BST and Back to MSMW, should I restore from a clean MSMW on your next version?
@Ian also when in admin and looking at Pages with the updates to WP php I cannot access, for example the Shortcode generator, nor the options of choosing sidebar and the text/visual on the page just defaults to text. Visual does not work.Posted 6 days ago #
Hi @MacMyDay. You should not have issues with v1.0.2.
In the BackStop Themes v1.0.1 I had renamed the themes. I had forgotten that WordPress is not portable across different themes w.r.t widgets so I changed the internal theme names back to their MSMW names and released v1.0.2.
NOTE: Remember to save any custom skin files before the upgrade. For some reason the MSMW designers decided to store custom skins in a theme folder that gets overwritten on a theme update! After the update copy the custom skins back to the theme folder.
TimPosted 5 days ago #
You must log in to post.