Updating from KrafterPRO V1.1 to Plugin V2.0.10 Questions
I watched the videos a few times and am confused. Can someone provide a step-by-step for a scenario like mine, where I already have my variables customized (links, colors, images, numbers). I also already have customized my own theme Builder templates so do not want to get over-written. The site is halfway completed.
After I would install the plugin, then install/import the V2.0.10 Variables JSON (Design System), I assume I should select "Merge" mode and preview what the NEW JSON wants to ADD to my existing. DO I skip this step altogether if I'm happy with my customized Variables?
So in general, am I installing the plugin, mainly for the UI in my situation or does the V2.0.10 bring any brand new variables that were not included in V1.1?
I have a similar situation where I am halfway through a redesign on a project and I installed the plugin with the JSON. I just rolled with it expecting I can reset the items that were overwritten and the trade off would be an improved UI consistency. I thought I saw something about being able to reset the colors etc. But I struggle to find it with what I have set up. I wonder if it would just make sense to edit the things we want to change in the JSON file directly. Still exploring but looking forward to sharing any findings I have or picking up things form responses here.
At the moment, members have only been upgraded from version V1.1 to V2.01
There were a few issues reported with this latest version, V2.01.
Mark and a member of the community worked hard over two or three days to fix them.
That is why yesterday’s video announced the new version and outlined the different versions he had released, which included numerous fixes and improvements. That’s what you have to do when developing a plugin: document the successive stages.
We members didn’t receive the various intermediate versions because they weren’t ready for release at each stage of development.
Mark documented them in different versions corresponding to each stage of correction.
Yesterday, Mark gave a presentation on what the new version will bring, with the aim of releasing it this evening as normal, and announced that he would make the file available for download the following day.
Among other things, the new version will enable the import of colours and fonts, which did not work with V2.01
Version 2.0.10 should be released within the next few hours.
Please wait until you reach the exit.
\
It is now Wednesday, that day following the release date for V 2.0.10 and when I clicked download, the file is still KrafterPRO_v2.0.1.zip. Did it not drop yet? I didn't see any update to his announcement.
Indeed, the new update is not yet available.
Mark did not communicate. A small message to say, there is a delay or wait I still correct a few things, would have been good for communication with members.
We are all looking forward to the exit. I think it's in progress.
I downloaded the file a few minutes ago, there is no plugin in it and the 2 files dated February 3. It must be an old version of Krater.
Jim Kemble Tierz Leger I believe the plugin you are looking for is inside the zip file. It seems counter intuitive at first for a downloaded zip file to need unpackkng to get to a zip file inside that contains a plugin.zip, a json file for importing templates from Divi theme builder view, and another JSON file for the variable presets to be used with the design system (I count on messages here to guide me bc I don't have the patience to watch the entire videos - but there are some useful nuggets anout these thing in the videos.
I'm not complaining but yesterday, at the beginning of the day, the version was V 2.0.1 and we were awaiting v 2.0.10 and just now it is V 2.0.19! That scares me a little. Luckily I was working on other jobs today, or I would have committed to V 2.1.10 which became greatly outdated in a few hours.
Would working with V 2.0.10 have been an issue?
Jim Kemble It isn't major changes when you are dealing with versioning that doesn't touch the first number (2 in this case) and the zero in the middle. A version change after the last number ("1") indicates to me that it is a minor fix. It shouldn't be a major impact. With changes to wordpress plugins usually you don't see site breaking changes unless there is a jump in those first two numbers. With the pace of changes happening lately it can seem unsettling but you should be able to take some comfort in the versioning number being low. When 3 hits the earth might move a little but you will be on the cutting edge as a pioneer 😜.
Sam Crowe That makes sense. Thanks.
Jim Kemble Just trying to pay it forward bc I have certainly benefitted from conversations on here and feel compelled to contribute.😀