Tomorrowland science museum of the city of arts and sciences in valencia

Casey Newton: Well I guess technically I am more qualified...

Frank Walker: Are you? How so?

A quick note from the road, Sentry is a fantastic error tracking that helps developers monitor and fix crashes in real-time. A few months ago, I created XT Sentry for Joomla for the Joomla Extension Directory (JED), a simple extension to install the client library to integrate the service: https://github.com/anibalsanchez/XT-Sentry-for-Joomla/releases

Integrating Sentry's error handler in Joomla template error page

We have implemented it with great success on Joomla Extension Directory (JED). However, a user reported an error that has not being received in Sentry's reports. Looking for an answer, I've just noticed that errors received and formatted at the template error page are not processed further. To solve this case, this snippet of code can be dropped in the template error.php:

After publishing XT Tailwind for Joomla (anibalsanchez/XT-Tailwind-for-Joomla, XTTJ for short), I have been receiving questions about Tailwind CSS and how to implement it on Joomla. I have summarized them here for future reference. These are the frequently answered questions:

If I build a site with XTTJ, are the other extensions compatible?

No. Most Joomla extensions are currently built based on Bootstrap 2 and jQuery. XT-Tailwind-for-Joomla does not load Bootstrap and jQuery (or any other library or third-party script) to keep the template minimal in the implementation of the original Tailwind CSS distribution.

Are you building a "generic template" with Tailwind?

No. At this point, we are developing several sites using this project (anibalsanchez/XT-Tailwind-for-Joomla) and adapting it to our requirements. Since the toolchain has node, PostCSS, Webpack, and other tools not meant for live sites, then porting XT Tailwind for Joomla to a LAMP site is not possible.

In general, Akeeba backups are infallible. I'm used to moving backups between servers blindly, with the kickstart restore or the Unite command line. However, MySQL GEOMETRY fields are a hard case. It seems that MySQL 5.6 - MySQL 5.7 transitions are rough.

Restoring a backup on a MySQL failed due to a POINT field. After searching, it seems that there's no solution, and a POINT field can't be exported and imported between MySQL versions.

# Failed with error: 1416 -- Cannot get geometry object from data you send to the GEOMETRY field

In this particular case, I'm lucky. The extension (JCalPro) that uses the POINT field also stores the original Latitude and Longitude. So, the POINT field "latlng" can be reconstructed with: