Trombinoscope Contacts v3.0 free and pro will bring a truck load of improvements and new features that I could not wait to share with you. The beta testing will open soon!
Joomla! 3 is packaged with Bootstrap 2.3.2, which is the latest Bootstrap 2 version ever released.
Simplify Your Web extensions, ever since the beginnings of Joomla 3, have been using the version of Bootstrap included with the Joomla core.
Although all versions of Joomla 3, for the sake of compatibility, remain on Bootstrap 2, more and more templates have evolved and moved on to use Bootstrap 3 or the latest Bootstrap 4.
PCI-DSS (Payment Card Industry Data Security Standard) is a set of security standards that websites have to follow in order to be able to process credit card transactions.
Generally, a third-party security assessor conducts the tests and generates a PCI compliance report, examining the physical infrastructure of the website, its access and potential code vulnerabilities.
The Joomla! platform is more secure than ever but third-party extensions and vendors may still have code issues that may need to be addressed.
There is a new kid on the block and this is one that is aimed to take advantage of the new picture background feature introduced in the Trombinoscope view and the module of Trombinoscope Contacts (free and pro).
Show a background image (a default image, the contact itself or any media custom field in Joomla! 3.7) behind any contact picture and make the contact cards more attractive and colorful.
There is a great feature that comes with Joomla! : the ability to override components, modules, layouts or even plugin outputs.
While this is wonderful for adding your own code snippets into the core components or other extensions found in the Joomla! Extensions Directory, the convenience and flexibility of it slowly becomes a burden overtime.
Starting with Joomla 3.7, custom fields have given websites the ability to add fields to contact forms. While the rendering of those fields looks alright in the administration console, you may end up, in the live part of the site (or frontend), with unexpected outputs (radio buttons not skinned, lists not showing…).
Once in a while, I am asked specific questions about modules. The user thinks there are problems with the module while the issues are actually template related. Those questions come from a confusion that is originated by the way module parameters are presented to the user in the Joomla console.
Page 2 of 3