Fooman

4.9K posts

Fooman banner
Fooman

Fooman

@FoomanNZ

Known for creating trusted #Magento extensions to save you time and money. Led by Kristof, proud member of @ext_dn and 3x Magento Master. #eCommerce

New Zealand Katılım Mayıs 2008
2K Takip Edilen3.3K Takipçiler
Sabitlenmiş Tweet
Fooman
Fooman@FoomanNZ·
We have been busy since the beginning of the year to ensure that all Fooman extensions will be compatible with Magento 2.4.6 including support for php 8.2. when it comes out. Happy to announce that all our extensions have been tested and updated to work with 2.4.6 / 8.2.
English
1
1
13
826
Fooman
Fooman@FoomanNZ·
@MarkShust Okay so now use the event sales_order_collection_load_after and that works. But now you also want to do the same for invoices. But alas there is no such events for invoice collections as the _afterLoad function is overwritten: #L66" target="_blank" rel="nofollow noopener">github.com/magento/magent…
English
1
0
1
181
Fooman
Fooman@FoomanNZ·
@MarkShust How much time do you got? A recent example: Let's try to append extension attributes to a list of sales objects. Great let's add a plugin on OrderRepositoryInterface::getList(). Unfortunately there are lots of invocations via OrderCollection which will miss out.
English
1
0
0
129
Mark Shust
Mark Shust@MarkShust·
What is your favorite part of Magento? What about your least favorite?
English
4
0
4
1.4K
Fooman retweetledi
Space 48
Space 48@Space48ers·
We're bringing Magetitans back! Which city would you be more likely to attend?
English
6
14
15
0
Fooman retweetledi
Luke Collymore
Luke Collymore@lukecollymore·
I saw someone in the Java community offer a free online workshop in @gitpod and how to use it in your development workflow, would anyone in the #magento community like to attend the same if I organised one?
English
7
6
18
0
Fooman retweetledi
Willem_Wigman::tweets.phtml
Willem_Wigman::tweets.phtml@willemwigman·
Join us tomorrow to hear real life experience on #spa #mpa #pwa #monolithic #composable #headless and ✨everything in between✨ When does it make sense to use each technology? We try to answer it tomorrow! Speakers: @lukecollymore @cmuench @jissereitsma @filrakowski and me!
Magento Association@MagentoAssoc

It's not too late to register for tomorrow's webinar "The 2022 #eCommerce Landscape Explained!" Starting at 10:00 AM CDT, this is your chance to clear up some of the misconceptions and confusion around the modern eCommerce landscape. bit.ly/3bNym8n.💻

English
2
13
12
0
Fooman
Fooman@FoomanNZ·
@gaiterjones You can always zip up from your own composer install. I suggest using the composer platform config #platform" target="_blank" rel="nofollow noopener">getcomposer.org/doc/06-config.… to make sure you match your production environment.
English
0
0
0
0
Fooman
Fooman@FoomanNZ·
@gaiterjones They removed them a while ago. I think it's for the better as there are always subtle differences depending on what version of php you are using. Offering 2+ versions for each Magento version gets cumbersome and error prone really quick.
English
1
0
0
0
PAJ
PAJ@gaiterjones·
what has happened to the magento 2 source packaged zip and tar downloads? 👀
English
3
1
0
0
Jo B
Jo B@saas_boss·
Who needs google ads when you have this 🙃
Jo B tweet media
English
5
1
16
0
Fooman
Fooman@FoomanNZ·
@mindpiss Fair comment. It’s good for business continuity for a small business.
English
0
0
0
0
Fooman
Fooman@FoomanNZ·
Must be Friday. Just been sitting in front of my computer trying to update software on my laptop for the last 30 minutes only to realise it's my previous laptop.
English
2
0
6
0
magetalk.phtml
magetalk.phtml@MageTalk·
Literally everyone who knows @BenMarks loves him. There are no exceptions.
English
1
1
9
0
Fooman
Fooman@FoomanNZ·
Rest assured that any automatic exports that did not come through during that period can be easily re-queued using the "Reset Xero Status" action.
Fooman tweet media
English
1
0
0
0
Fooman
Fooman@FoomanNZ·
Unfortunately our legacy infrastructure for our Fooman Connect Xero integration just experienced a minor outage due to a DNS issue at the hosting provider. Details here status.heroku.com/incidents/2453
English
1
0
0
0