Joomla news about Digital Peak

The restricted DPMedia filesystem plugin stores images automatically on a specific folder with the article or category ID in the filesystem path. When the media manager is opened from within the article form, then it shows only the content of the respective folder without the whole tree of the images folder. That prevents publishers navigate outside and to mess with the images folder, everything is nicely structured.

Previously did the restricted adapter store the images always in a path with the full context name (com_content.article), some user were arguing that it is a too technical approach. Now it is possible to add a substitute name for the context to have it in a more user friendly way. This is especially handy when you have a blog and images are always connected to one blog post, so the images will then be stored in the folder /images/blog/{id} and not /images/com_content.article/{id}.

More information can be found in the context concept documentation.

The restricted images adapter for the Joomla media manager stores the images automatically in a path with the article ID. When a new article is created it was not possible to upload images, only when the article was saved at least once. This was problematic on large web sites where users could create articles and publishing was done by an admin. Now are images uploaded to a temporary directory and when the article got created, they are moved to the correct location automatically.

More information can be found in the restricted plugin documentation.

When an image is uploaded to SmugMug, then it is stored in different sizes in their cloud. The DPMedia plugin was always using the original size which is often too big for performance optimized web sites. Instead of the original size, can now a default size be specified in the adapter. Images not nigger than that size are used, when they are selected in an article or banner. Like that it is possible to have all images with the same size, in a way that they fit perfectly your Joomla web site.

This feature is only used when no local images are configured. If local images is enabled, then does the plugin copy the image from SmugMug to a local folder and serves it from there in Joomla, which improves privacy on your web site. More information about all these features can be found in the SmugMug plugin documentation.

When external events are configured with database sync, the eventsync.php script must be executed as cron job to perform that long running task. This is a legacy from the Joomla 3 ages and nowadays cli scripts should be converted to Joomla scheduler tasks. They are easier to maintain in the web interface and failures are notified by mail.

Therefore, we have deprecated the /administrator/components/com_dpcalendar/cli/eventsync.php file and are offering now a scheduler task which does the same job. Once the task plugin is installed, a new task can be created and an external calendar selected. This task should be executed shortly before the cache expires in the plugin to prevent admins from hitting the sync task while browsing the web site. More information can be found in the task plugin documentation.