Wakanda older widgets within web components (on which mature applications are based) are not displaying properly. This was initially observed with 1.0.3, and initially 1.1.0 (pre-release) corrected it. But with the latest official 1.1.0 release, this issue has returned. The behavior is browser independent. Wakanda Server running on OS X.
I have had to freeze the version of Wakanda to 11.194922, which does not result in this behavior.
When I inquired about this previously, I got perspectives suggesting that the widgets are "deprecated." Those that suggested this seem to be comfortable with the idea that years of developed mature apps on Wakanda can be "redeveloped." This is not feasible in my case, and poses a show-stopper if this is a non addressable issue.
Can someone from the Wakanda team give me a clear input on this?
Thanks ...
Related
Intro :
as the title suggests. I am starting a new e-commerce website using magento, the latest available release on official website is 2.1.7, I've just learned that the 2.2 version will be soon released,holding decent code changes.
I am not very familiar with magento and I hear it is not as easy to upgrade as other CMSs like wordpress.
I know php,mysql etc.. but I don't want to spend a lot of time immigrating.
The question is:
should I wait version 2.2 to be released or just go for 2.1.7 and upgrade later?
You can start now with magento 2.2, at this moment it is already RC, the changes over 2.1 are many, so the first thing is to verify if the manufacturers of the extensions or theme that you are going to use already have compatibility.
http://devdocs.magento.com/guides/v2.2/release-notes/backward-incompatible-changes.html
The answer to this class of questions ("Start with version X.A or wait until X.B?) is always get started now! A dot release won't be a rearchitecture, so any knowledge you gain in working with 2.1 will be applicable to 2.2, and you will learn things and improve your skills by starting with 2.1.
I need to install and set up step by step the varnish cache in an application in OpenShift , but I do not know where to start and not the steps for this. Can anyone help ?
If you mean OpenShift Online in current production version, it's older version 2.x, based on RedHat's own container technology.
If you have OpenShift Origin or OpenShift Enterprise or OpenShift Online Developer Preview, probably it's version 3.x, and it's based on Docker.
You can definitely tell which version are you using by looking at CLI tool's name. If it's rhc, it's older version 2.x, if it's oc, it's newer Docker based.
For newer Docker base, you should be able to deploy any docker image, so varnish should be no problem at all.
You just have to build your own docker image and follow OpenShift tutorial to deploy it on your platform.
I started to play with it, but don't have enough know-how to provide you with step-by-step tutorial right now, maybe in a week or so.
However, if you are using older public version of OpenShift Online, I have a bad news for you.
I've tried to compile static version of varnishd, no luck till now. And I'm not going to try anymore, because fully static version of varnishd is not possible at all, as it's based on dynamically loading of compiled VCLs, thus should be dynamically linked to OS libraries.
And this could be a bit hard to achieve. You have to match correct versions of OS libraries and still it's fragile as it could possibly break after upgrade of underlying OS.
I wouldn't try this in production.
I suggest you to try another could provider, either IaaS solution with full OS with varnishd installed from packages, or choose any Docker hosting provider.
Or, if you can afford it and it's worth for you, you may try http://fastly.com/, a CDN provider.
Their technology is based on customized older version of varnishd, with easy to use GUI, a lot of fancy built-in stats, etc... But the most important feature is you can deploy your own VCLs upon request. If they enable it to you, you can upload new VCL in few seconds.
Good luck.
I have gone through google and also through solutions provided here but I am not able to install zend framework 2.2.4 with xampp 1.8.1.
Anyone please let me know how to install this as I am currently feeling that installation of zend framework is impossible.
There are lots or resources out there and even if the approach of installing differs a little, it's practically all the same. And it's impossible for there not to be an error message, as all the tools used in the installation process of ZF2 on Xampp are pretty good when it comes to their respective error messages, be it appache itself, git or composer. They all give out decent error messages.
As hinted by Fozzy there's one high traffic post on ZF2 here on SO:
Installing Zend Framework 2 on XAMPP in Windows
And there's also another good enough tutorial over there on the official documentation from ZF2 itself (non Xampp specific)
http://zf2.readthedocs.org/en/latest/ (See Installation and the first two User Guide Chapters)
I have a website that uses YUI 3.3.0 and YUI 2.9.0 (using YUI 2in3 project), right now I'm trying to improve performance in the initial load time of the site, I followed several tips that I found on the web, but I wonder if I have any improvement if I make an upgrade from YUI 3.3.0 to YUI 3.7.1
What's the difference? YUI 3.3.0 was released in January 2011, and 3.7.1 in September 2012, so that is ~20 months of work by the YUI team and community on the library that is missing (4 versions). Since YUI has hundreds of modules, it's tough to pin-down exactly what changed that could affect your site. It could be very little, or it could be a lot. It's very unlikely that an upgrade could slow-down your site, though. Performance has always been a high priority for the project, so whenever performance wins can be had, they are taken. For example, this recent 3.6.0->3.7.0 introduced some significant custom-event performance improvements (source).
You can take a peek through each release announcement to see if any of your specific needs were addressed:
3.4.0
3.5.0
3.6.0
3.7.0
Also, stop by #yui on Freenode if you have any specific questions about your site and YUI performance.
As the question states, I am preparing to deploy my first couple modules on the Magento Connect store and want to make sure I am targeting the best versions. Testing on 1.3 is proving to be a bit of a pain, and if only a few people use that version I would rather spend the time making the modules better!
Google hasn't helped as yet, though I think the keywords I use are getting picked up as other more specific technical questions (Google Base, for example).
Does this information exist? What about your personal experience? For me, I have only encountered installations below 1.5 Community (1.10 Enterprise) for upgrade projects. I haven't personally encountered a client that is on 1.4 and plans to stay on 1.4.
Thanks!
Tim
There are a signification amount of people who have older versions and wont upgrade because of the complexity and the amount of modification they have done to their stores.
Most people right now who are on community version seem to be on 1.5 or 1.6, but if you want to test older versions just download from the archive install locally and see if it works for the older versions.
Here is a link to the downloadable versions of magento, in case you decide to test on those older versions:
http://www.magentocommerce.com/download - click released archived tab at the top