In this article, I'll show you how to manage an Acy Mailing 5 subscription list.

Access to Acy Mailing 5

This is screen accessible via the administration area: Select Components → Acy Mailing 5 → Lists from the drop-down menus.

Newsletter lists

Presently there are six (6) list items:

The generally accepted answer to a mysqldump is:

mysqldump -h [host] -u [user] -p [database_name] [table_name] > [file].sql

Or a variant there of...  Of course if you are logged in to the server and working from it you don't need to express the -h [host]

mysqldump -u [user] -p [database_name] [table_name] > [file].sql

Working in Twig, I had to add classes to a pre-existing array.  Whilst I've grown used to the patterns in PHP, these cannot be applied in Twig.  Instead I had to merge the new array elements.

Non associative arrays

Working from a base level, I'll begin as if the original array hasn't been set.  The merge filter expects as first argument an array whose content will be merged with the assigned variable:

In this article, I will show you how to update an existing member's details using Community Builder.

Access to Community Builder

This is screen accessible via: Select Components → Community Builder → User Management from the drop-down menus.

Adding a new user to your Joomla! website using Community Builder.

Out of the box, users are managed via Joomla!'s user management system.

Access to Joomla!'s user system

This is screen accessible via: Select Users → Manage from the drop-down menus.

However, in this instance we won't be using Joomla!'s solution.  Instead working with a component called Community Builder.

Cached data - keep it or clear it out?

You might have noticed, but when opening an app or visiting a website for the first time can take longer than on a subsequent visits to the same site. This extra time taken is primarily due to our devices not having cached data for the website or app.

There are times when other Joomla! administrators of the site leave a page without tapping one of the methods to close it... save & close or close.  Subsequently, when a page hasn't been closed, a padlock appears to prevent another administrator's accessing the page(s) to make changes.  Great for content management, not so great if the person is uncontactable.

On a git pull from remote dev environment to a staging environment running off AWS server... I was greeted with the white screen of death.  While it took me a while to resolve the actual issue, my action plan was as follows:

How to resolve:

1. Look in your log files;
2. Add a few lines to your index.php file

Creating URL's in Drupal programmatically:

Internal path

use Drupal\Core\Link;
use Drupal\Core\Url;

$internal_link = Link::fromTextAndUrl(t('Drupal nodes'), Url::fromUri('internal:/node', $options))->toString();

External Url

use Drupal\Core\Link;
use Drupal\Core\Url;

$external_link = Link::fromTextAndUrl(t('Codebales'), Url::fromUri('http://www.codebales.com/'))->toString();