SSL Labs ScoreSecurityHeaders.io Score

I went onto the JED to publish a new extension, and found that I'm not allowed. Apparently, at some point in the past, a Joomla Extension Directory administrator unpublished one of my extensions and that restricts me from publishing a new extension.

I never received any notifications that this happened, so I don't even know when it occurred. There isn't any information about why it happened (as the JED used to provide) so I don't know what even to look at. Without having any indication of the issue or notification that it even happened, I'm left to wonder if this isn't malicious.

Lately, Joomla has become hostile to 3rd party developers. I've been criticized by core developers for releasing paid extensions on a number of occasions, and seem to be ignored when I point out that 80% of my extensions are free. I haven't met any Joomla developers who aren't evangelists to the platform - so why the hostility?

Django + React is looking like more and more appealing.

Discuss this article in the forums (0 replies).

No, I'm not doing it!

Microsoft stopped supporting these browsers January 12th 2016. I am not going to bend over backwards to support a browser that isn't even supported by the company who made it.

Like IE6, IE 8, 9 and 10 were horrible browsers. IE 11 isn't much better, and although I can't say I like Edge - at least it attempts to support modern standards.

My efforts will be spent making my software compatible with the major supported browsers. IE 11, MS Edge, Chrome, Firefox, Safari and Opera

Discuss this article in the forums (0 replies).

I've been deep into GDPR compliance extensions for Joomla recently, and while setting up a demo site I realized that compliance meant I had to give up Google Analytics. Anyone who runs a website knows this is unacceptable. Sure, there are other ways to obtain the information, but Google has really built a fantastic tool to monitor all sorts of data, not just about the visitors - but also traffic sources, time spent on specific pages, browser capabilities, and gobs more information.

That darn GDPR though - requiring consent prior to placing cookies is a killer. How do you know what content is engaging your visitors when all you have to go by is a hit counter?

So I set out to remedy that situation using a bit of knowledge I picked up years ago. Google Analytics doesn't need cookies. Over the course of 14 hours I built and tested my newest extension - System - Google Analytics (Cookie Free)

I had to be careful with certain configurations, because the goal was to achieve analytics without running afoul of the GDPR regulations concerning collection of personal data. The result has been fantastic, and I was even able to watch www.cookiebot.com scan the site for EU regulatory compliance.....how do you think I did?

It's running on this site now and soon all of my sites. Hopefully, when it's approved in the JED, it will start appearing on sites all over the EU.

Discuss this article in the forums (2 replies).

I've been tracking some bad reviews in the JED for one of my more popular extensions. What I'm finding is very unfortunate, because there isn't much I can do about it other than beg people to stop. Apparently, people are creating non-forks of my extensions and then leaving them online to become stale, or are linking to the download destination of specific versions of my extensions. I don't know if this is malicious, or if they're just oblivious to the consequences of their actions. Of course they would be oblivious - they aren't the ones feeling the consequences.

I release updates for bugfixes on a frequent basis. Feature releases are less frequent, but all the same - my extensions get updated regularly. When someone creates an un-maintained/un-altered fork, they're creating a scenario that makes me look bad. Someone downloads the bad fork, and when it doesn't work - they blame me for it.....leaving bad reviews in the JED. It doesn't hurt the person who created the fork, so why would they pay it a second notice? Likewise, when someone links to a specific old version of my extensions, people download it expecting to see a working extension - which is not always the case where Joomla is concerned. Updates to Joomla drive many bugfix releases. If you download the 2.14.0 version of my extension, but I've released over 100 updates since then - you're not going to have a good experience.

Please, please! If you're going to link to an extension - link to the download page. If you're going to fork an extension - do it the right way. Don't leave my name on it - I don't want the blame you're creating for me.

Discuss this article in the forums (3 replies).

I've spent several days troubleshooting issues for people who downloaded my free extensions. In every case, the issue was caused by their bad decisions and poor implementations.

Here's a tip to avoid wasting the time of someone who is, essentially, doing you a favor by giving you free software. Before you send email, or post to a forum, or write a bad review - do a reality check. Ask yourself the question - could it be something I did? When all of the reviews are good, and you can't make it work - chances are that you're doing something wrong.

A way you can check is to perform a clean install. A fresh installation with no additional software, just the core - and the extension. Follow the instructions. If it works, then you know it's your fault and not the developer or the software. If it doesn't work, then make your accusations (but be polite about it).

Discuss this article in the forums (0 replies).