Almost a year ago, I published Pagebuilder by SiteOrigin Widgets on Steroids. Now, I’m very excited to tell you that Extended Widget Options now also provides management solutions for Elementor widgets. This new beta feature that supports Elementor Pagebuilder is also available on the plugin’s free and extended version. Elementor is growing fast. This page builder is loved by lots of users. That includes me, of course. It uses widgets, which means there’s room for boosts using Widget Options.
Honestly, I had tried to combine Widget Options with Elementor before. However, there had seemed to be lesser hooks. In addition, their APIs had been constantly changing. It had been a failed attempt until last month. I found out that I could at last extend the plugins’ functions to it.
How Widget Options Work with Elementor Widgets
Let’s start with Widget Options – the free version. Let’s see how we can extend each Elementor’s widget. First, let me list the features of this version :
Show or hide widgets on specific WordPress pages
Restrict widget visibility per post category
Show or hide widgets per taxonomy
Manage widget visibility by conditional
Continuing our series of progress reports which aim to track the ups and downs of a fledgling venture, this post shares the details of how the past month has gone, what we have been up to and what we have planned for October. Do we start calling these income reports?
We started off September with the release of some premium WordPress products, namely our Really Useful Notification Bar on CodeCanyon and our first premium theme release on Mojo Marketplace, Hames for WordPress.
In keeping with our relentless pace of releasing high quality freebies too, September saw us unleash a free version of our Really Useful Bar over on WordPress.org.
With Envato essentially killing off the marketplaces and authors who built it, sales over there are unsurprisingly flaccid, but we are happy to add to our overall presence so we will continue to use them as a vendor of our products where possible.
Where has this left us? Well, as of typing we have earned a whopping $87 dollars in sales so far, which we hope with some solid investment we can turn in to $87.01 in no time, guffaw.
Now, before I get into this, I need to stress that this is a new project and we are not splashing cash on ads
With internet, the world is smaller than ever. But taking advantage of that still is a challenge. Yes you can easily talk to foreign people, drive traffic on your website from foreign countries, and translate your website with a tool like Weglot.
But increasing your returning visitors, your subscribers, or your customers (depends on who you are and your main KPI) is more than just driving traffic.
It is about creating value to your new targeted audience. And to do so, you could need more than an English website.
Who are you?
Internationalizing your website will be different if you are an ecommerce, a SaaS, a blog etc…In fact, the key factor to study here is whether you could target the whole Internet Nation at first, or if your website had to start by targeting a local audience. If you are:
In this case, it is pretty easy to internationalize your website if you are an English-speaker, or if you know the language of your foreign target audience. If you are willing to invest in professional translation, it will be even easier.
The only two challenges you will face are translating your website and adapting your content to your foreign audience. Translating your website could
Knowing that React is a very strong contender for Gutenberg I decided to get the other side of the story as well. i.e., how does the React team feels about it things that we (WordPress Community) care about?
I had an incredible chat with the React team — Dan Abramov, Andrew Clark, and Sophie Alpert. They were keen enough to share thoughts about React.js and WordPress.
Have at it.
How can a system fundamentally evolve without drastically changing? WordPress can build incredible sites, yet the usability and clarity that used to be a driving force for its adoption has been fading away. The present reality is that many people struggle using WordPress as a tool for expression—they struggle to compose richer posts with media, to get their site looking the way they want, to imitate how a theme demo looks, or to set up and customize a store. There is a disconnect between what is edited in a given field somewhere in the interface with how it will look on the real site. WordPress has always been about the user experience, and that needs to continue to evolve under newer demands. Gutenberg is an attempt at fundamentally addressing those needs, based on the idea of content blocks. It’s an attempt to improve how users interact with their content in a fundamentally visual way, while at the same time giving developers the tools to create more fulfilling experiences for the people they are helping. How can such a vision happen without dismantling, rebuilding, fragmenting, or breaking the WordPress ship that for over a decade has been carrying the thoughts, joys,
Introducing Move Widget – a brand new way to manage your WordPress widgets easily. With this new feature, you can now have an alternative and better way to move widgets around. Together with Clone WordPress Widgets, I’m very happy to introduce the better widget management release for Widget Options.
Don’t get me wrong, I love the “widget drag & drop” feature. However, when you use lots of sidebar widget areas, it’s hard and time-consuming to drag and scroll the page just to move it around. Will it be a lot easier to just move them just like how we add them? I’m sure that you know how we add widgets to any sidebar. First, you click on the widgets. Afterwards, you select the sidebar where you want to assign them to. It’s really easy, especially on mobile devices or when you have lots of widget areas. Now, you’ll have this feature with Move WordPress Widgets, which is available for both free and extended plugin versions.
How to Enable Move Widget
By default, this feature isn’t enabled, but you can easily activate it by going to Settings > Widget Options. After that, on the Move Widget feature module, click on Enable.
For background, WordPress, which I love, but bless its heart, for some reason still supports PHP 5.2, which hasn’t had security support forever. I’m pretty passionate that if WordPress wants to be the serious application platform we all want to claim its become because REST API, than dropping support for PHP5 in core, is an important signal to the developer community that developer experience is going to be prioritized. Also, I pride myself on really tweaky bug reports and patches. My favorite is the patch I wrote to reduce the loops that run when metadata is saved from 4 to 2. That or some inline documentation updates in \WP_Query.
Also, I’m experimenting with acceptance testing using Ghost Inspector, which is a really cool name for a SaaS. They give you a really simple looking way to record and run acceptance tests and I think using this tool will be easier to set up and maintain then learning/deploying/using Selenium, which I’m sure they are using.
But, this isn’t about acceptance testing with Ghost Inspector. I’ll report back on that once I figure that out, either here or on Torque. Anyway, this post is about how I registered a widget, inside an an anonymous function, using an anonymous