JavaScript Archives - schmengler-se.de

28. March 201613. January 2020

The week on StackExchange #12 / 2016

Here’s the next update, this time only with new, hopefully interesting answers on Magento StackExchange.

Magento 2

Which compilation commands are needed in developer mode and when? received a few useful answers. The +150 bounty for the best canoncial answer is still open.
I shared some thoughts about efficient usage of builders: Use preconfigured builders (e.g. for SearchCriteria) in Magento 2 Thanks to Vinai for helping out here!
Do you miss good old local code pool overrides? Read this: Override abstract class in Magento 2
Confused with the mixture of $(), $$() and jQuery() in JavaScript? What does $$ in javascript of Magento 2 mean?

Magento 1

Saving CMS pages and blocks programmatically (e.g. in a setup script) can be tricky: Saving CMS block/page from collection removes store ID’s
Somebody couldn’t overwrite template via xml added by external module – a common pitfall with the layout XML when block names are reused.
And a quickie, which events to observe to react on cart changes: Is there an event that fires when the cart/quote is empty?

21. March 201613. January 2020

The week on StackExchange #11 / 2016

Here’s the next update with new, hopefully interesting, questions and answers on StackExchange.

New Answers

If you are wondering wether to import classes with “use” or use the fully qualified class name, read Magento 2: use statement versus direct class path?
What happened to the customer_logged_in and customer_logged_out layout handles in Magento 2? Magento2. Layout Handle customer_logged_in
If you want to set up a password protected staging system with Varnish, here you go: Setting up Magento Staging Environment with Restricted Access
My question on translation scopes in Magento 2 finally received an answer with a somewhat satisfying solution for translation conflicts: How does translation scope work in Magento 2?
A quickie: The best way to react on changed configuration values in Magento 1: How to detect changed fields only in admin section?

New Questions

After a day of Magento 2 develoment with JavaScript, I shared the frustrating summary on Twitter, which attracted some attention:

Today's Magento 2 workshop: 3h installing, 1h explain DI, plugins & Co, 2h coding & debugging, 2h waiting for static content to be deployed

— Fabian Schmengler (@fschmengler) 18. März 2016

Looks like I am not alone with this experience but it’s not really how it is supposed to be. This lead me to the question Which compilation commands are needed in developer mode and when?
There seems to be a bug in certain Magento versions with order reports and timezones but I could not quite pin it down yet: Magento Reporting – Is it bucketing by UTC?

4. August 201413. January 2020

Magento Testing: Fill Forms with one click

Who doesn’t know this situation: When testing features like the guest checkout manually, you have to fill all form fields tedously again and again. With Chrome auto complete or “test”, Ctrl + C, Ctrl + V it’s halfway fast but still a bit annoying. And what if the test data is supposed to make sense and should not be the same every time?

Inspired by this article on css-tricks.com I developed a little Magento module, that enables filling Magento forms with dummy data with one mouse click. Currently it is implemented for billing address and shipping address.

Github-Repository: SSE_FormFiller

And this is how it looks:

Screenshot: Forms in Checkout

Configuration

Of course you want to see this button only on your development system, that’s why there are two ways to hide it: Either disable the module completely per configuration or show the button only in developer mode:

SSE_FormFiller Configuration

The nice thing about the second variation is that the JavaScript still gets loaded, so that you can substitute the button with a bookmarklet. Here the snippets:

Billing address form

JavaScript:

formFiller.fill(billingForm.form)

Bookmarklet (right click, add as bookmark!)

Shipping address form

JavaScript:

formFiller.fill(shippingForm.form)

Bookmarklet (right click, add as bookmark!)

Technology

A bit of information on the implementation:

The dummy data comes from Faker.js.
The button gets added to choosen blocks with an observer for core_block_abstract_to_html_after
In the JavaScript the form ID determines which fields should be filled.

The module is designed to be extended for other forms as well. Suggestions and of course pull requests on Github are most welcome! Continue reading “Magento Testing: Fill Forms with one click”