Plesk Service Team is pleased to introduce the Plesk FAQ.
We collected a lot of questions and answers concerning various aspects of Plesk in the corresponding KB article.
We will continue to fill Plesk FAQ with new and valuable information.
J and Beyond, an International Joomla! Conference, is back for a fourth year.
From May 31st to June 2nd, Joomla! developers and site builders from over 30 countries will gather in Noordwijkerhout, near Amsterdam.
J and Beyond is one of two big international Joomla conferences every year, with the Joomla World Conference being the other.
Come to J and Beyond for all these reasons and more:
The J and Beyond team are excited to have such a great and varied lineup of Keynote speakers including Pierre Joye from php.net who has made over 6000 commits to php.net.
It’s not just about the code – it’s about the relationships that are made. Chiara Aliotta will be speaking about the relationship between the designer and the developer and Xavier Dutoit will be there to build bridges between the Joomla and CiviCRM communities.
David Hurley (community development manager) and Andy Tarr (PLT) will be speaking on what have we accomplished in the past few years? Where are we in the current state of the web? Where are we going?
Finally there are two wildcards. Rod Martin and Peter van Westen will be bringing their unique, thought provoking and truly entertaining presentation styles with “Life Is Short And So Am I” and “What Nothing – Regular Expressions and other confusing s(?:tu|h[1i])([f]{2}|t)$”
Click here to find out more about our keynote speakers.
Noordwijkerhout, is very conveniently located. The venue is near Amsterdam and is only 25km away from the Netherlands largest airport, Schiphol
Well almost. The early bird ticket sales end at the end of April and with the money you save you can buy more beer (or soda).
Click here to buy tickets now.
You can only win a speaker slot if you enter the competition. If you were waiting for an invitation to speak: THIS IS YOUR INVITATION. Submit your session proposal today. The deadline is the 15th April (no exceptions).
This year we are offering three different session lengths:
We want you to present.
The following new features have been implemented:
[+] Running PPA behind NAT. Administrators can configure PPA to run behind a router with NAT.
The following features have been improved:
The following bugs have been fixed:
[-] Administrators could not register Windows-based service nodes if the administrator’s password contained the ^ symbol.
The following new functionality has been added:
[+] AWstats has been updated to version 7.1.1.
Note: New AWstats perceive wget as a robot.
The following bugs have been fixed:
[-] Error appeared after trying to edit default website widget in admin UI (133018)
[-] Phpmyadmin stuck when execute Update SQL query from GUI (132241)
Following check item has been added:
WordPress 3.6 Beta 1 is now available! This is software still in development and we really don’t recommend that you run it on a production site — set up a test site just to play with the new version. To test WordPress 3.6, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the beta here (zip). We’ve […]
The April issue of the Joomla Community Magazine is here! Our stories this month:
Listen Up!, by Alice Grevet
Interview with Community Development Manager David Hurley, by John Rampton
Joomla! is the People, by Helvecio da Silva
Interview with CMSExpo Founder John Coonen, by John Rampton
The X Factor and Women in Tech, by Dianne Henning
JoomlaDay Boston, No Blarney!, by Dianne Henning
Leadership Highlights – April 2013, by Marijke Stuivenberg
Progressive Enhancement: Flip the Script on Your Responsive Ways, by Ryan Boog
Tips to Find a Joomla Developer, by Johans Empuerto
Creating Call-to-Actions that Will Actually Get Action, by Hannah Kaufman
Easy To Use Joomla Search Operator Commands, by John Rampton
Head in the Tag Clouds, by Elin Waring
4 Ways Joomla Developers Can Monetize Free Extensions, by Pravin Daryani
Joomla! 3.0 Extension Development Series: More Functionality, by David Hurley
Joomla! 3.1.0 Tag Field, by Roberto Segura
CDNs for Joomla – A Beginners Guide, by Steven Johnson
Community Choice Extensions – UPDATE, by Dianne Henning
Post your Haikus for April, by Dianne Henning
Browse the international articles submitted this month.
We want to publish your Joomla! story in the next JCM issue! So take a look at our Author Resources content to get a better idea of what we are looking for, and then register to become a JCM author and submit your Joomla! story!
The Joomla! Project is pleased to announce the availability of Joomla! CMS 3 Beta3. Community members are asked to download and install the package in order to provide quality assurance for Joomla 3.1. Joomla 3.1 is scheduled for release on April 15th, 2013.
Joomla 3 is the latest major release of the Joomla CMS, with Joomla 3.1 the second short term support release in this series. Please note that going from Joomla 3.0 to 3.1 is a one-click upgrade and is NOT a migration. The same is true is for any subsequent versions in the Joomla 3 series. That being said, please do not upgrade any of your production sites to the beta version as beta is ONLY intended for testing.
This is a beta release and not for use on production sites.
Extension developers are encouraged to work with this release in order to prepare extensions for the General Availability release of Joomla 3.1, though there shouldn’t be any backward compatibility issues. Users are encouraged to test the package for issues and to report issues in the Joomla! issue tracker.
Miscellaneous: 28574 – Removed the GeSHi plug-in
Version 2.5 of the Joomla! CMS is a Long Term Support release and support for it will continue until shortly after the release of Joomla 3.5 scheduled for Spring 2014. Joomla 2.5 users do not need to migrate to Joomla 3.0 or 3.1.
Moving to Joomla 3.x from Joomla 2.5 will be a mini-migration not an upgrade, although for the core of Joomla! the migration should be simple. However, it is likely that templates for Joomla 2.5 will need modification to work with Joomla 3 as will many extensions. Always test prior to migrating and consult with the developers of any extensions and templates you use.
Support for Joomla 1.5 ended in April of 2012 and we continued to support it unofficially until the end of 2012 for medium to high priority security issues.
Does that mean your 1.5 site will suddenly stop working? No, your site will continue to work as it always has. However, Joomla’s developers will not be releasing new versions for Joomla 1.5, so you won’t be getting bug fixes or security fixes. For this reason, it’s recommended to migrate from 1.5.
Moving from 2.5 to any Joomla 3 version is relatively simple, since Joomla has made the process easy for newer versions. Unfortunately, moving from 1.5 is not a trivial task. Fortunately, there are two good extensions that make the process easier: jUpgrade and SPUpgrade.
You have a choice of going straight to Joomla 3.0 or going to 2.5 first. Both jUpgrade and SPUpgrade have versions ready for both versions. Please consult with their documentation on how to migrate from Joomla 1.5 to 3.0/2.5.
For most new/migrated sites, the Joomla! 3 series is the preferred series and starting on it avoids a mini-migration from Joomla 2.5 later down the road. Starting on the Joomla 3 series for a new/migrated site, also provides you with longer backward compatible support (with one-click upgrades) than starting a new site on 2.5 right now, because support for 3.x ends in 2016.
There are a variety of ways in which you can get actively involved with Joomla! It doesn’t matter if you are a coder, an integrator, or merely a user of Joomla!. You can contact the Joomla! Community Development Manager, David Hurley, [email protected], to get more information, or if you are ready you can jump right into the Joomla! Bug Squad.
The Joomla Bug Squad is one of the most active teams in the Joomla development process and is always looking for people (not just developers) that can help with sorting bug reports, coding patches and testing solutions. It’s a great way for increasing your working knowledge of Joomla, and also a great way to meet new people from all around the world.
If you are interested, please read about us on the Joomla Wiki and, if you wish to join, email Mark Dexter, one of the Bug Squad co-coordinators.
You can also help Joomla development by thanking those involved in the many areas of the process. The project also wants to thank all of the people who have taken the time to prepare and submit work to be included in Joomla 1.6,1.7, 2.5, & 3.1, and to those who have worked very hard on the Joomla Platform separation project.
If you are an extension developer, please make sure you subscribe to the general developer mailing list as this is a place where you can discuss extension development and news that may affect custom development will be posted from time to time.
Following is a list of previous news and information about Joomla and other sites of interest:
This beta release is the result of thousands of hours of work by dozens of volunteers. Thank you so very much for making Joomla the best CMS on the planet!
The following bugs have been fixed:
[-] Backup fails on dumping smb_users table if perl-DBD-mysql package doesn’t installed (129117, 129657)
[-] If custom database schema has been created inside database that database can’t be backed up and restored on MS SQL 2008 SP2 (125163)
[-] Installation of psa-kav8 package on CentOS/RedHat 5.9 fails after libxml2.so.2 update
Following check item has been added:
– add notice about all mail list members of all domains will receive welcome messages about being added to their mail list again
Following check item has been added:
– check for enough inodes on Destination server
The following bugs have been fixed:
[-] DrWeb mail handler runs two times on each message (108472).
[-] Upgrade php component breaks permissions on php sessions directory (91998).
[+] CentOS 6.4 support has been addded. There is know issue with switching between mail servers: http://kb.parallels.com/en/115779
The Joomla! Project is pleased to announce the availability of Joomla! CMS 3 Beta2. Community members are asked to download and install the package in order to provide quality assurance for Joomla 3.1. Joomla 3.1 is scheduled for release on or around March 25th, 2013.
Joomla 3 is the latest major release of the Joomla CMS, with Joomla 3.1 the second short term support release in this series. Please note that going from Joomla 3.0 to 3.1 is a one-click upgrade and is NOT a migration. The same is true is for any subsequent versions in the Joomla 3 series. That being said, please do not upgrade any of your production sites to the beta version as beta is ONLY intended for testing.
This is a beta release and not for use on production sites.
Extension developers are encouraged to work with this release in order to prepare extensions for the General Availability release of Joomla 3.1, though there shouldn’t be any backward compatibility issues. Users are encouraged to test the package for issues and to report issues in the Joomla! issue tracker.
Miscellaneous: 28574 – Removed the GeSHi plug-in
Version 2.5 of the Joomla! CMS is a Long Term Support release and support for it will continue until shortly after the release of Joomla 3.5 scheduled for Spring 2014. Joomla 2.5 users do not need to migrate to Joomla 3.0 or 3.1.
Moving to Joomla 3.x from Joomla 2.5 will be a mini-migration not an upgrade, although for the core of Joomla! the migration should be simple. However, it is likely that templates for Joomla 2.5 will need modification to work with Joomla 3 as will many extensions. Always test prior to migrating and consult with the developers of any extensions and templates you use.
Support for Joomla 1.5 ended in April of 2012 and we continued to support it unofficially until the end of 2012 for medium to high priority security issues.
Does that mean your 1.5 site will suddenly stop working? No, your site will continue to work as it always has. However, Joomla’s developers will not be releasing new versions for Joomla 1.5, so you won’t be getting bug fixes or security fixes. For this reason, it’s recommended to migrate from 1.5.
Moving from 2.5 to any Joomla 3 version is relatively simple, since Joomla has made the process easy for newer versions. Unfortunately, moving from 1.5 is not a trivial task. Fortunately, there are two good extensions that make the process easier: jUpgrade and SPUpgrade.
You have a choice of going straight to Joomla 3.0 or going to 2.5 first. Both jUpgrade and SPUpgrade have versions ready for both versions. Please consult with their documentation on how to migrate from Joomla 1.5 to 3.0/2.5.
For most new/migrated sites, the Joomla! 3 series is the preferred series and starting on it avoids a mini-migration from Joomla 2.5 later down the road. Starting on the Joomla 3 series for a new/migrated site, also provides you with longer backward compatible support (with one-click upgrades) than starting a new site on 2.5 right now, because support for 3.x ends in 2016.
There are a variety of ways in which you can get actively involved with Joomla! It doesn’t matter if you are a coder, an integrator, or merely a user of Joomla!. You can contact the Joomla! Community Development Manager, David Hurley, [email protected], to get more information, or if you are ready you can jump right into the Joomla! Bug Squad.
The Joomla Bug Squad is one of the most active teams in the Joomla development process and is always looking for people (not just developers) that can help with sorting bug reports, coding patches and testing solutions. It’s a great way for increasing your working knowledge of Joomla, and also a great way to meet new people from all around the world.
If you are interested, please read about us on the Joomla Wiki and, if you wish to join, email Mark Dexter, one of the Bug Squad co-coordinators.
You can also help Joomla development by thanking those involved in the many areas of the process. The project also wants to thank all of the people who have taken the time to prepare and submit work to be included in Joomla 1.6,1.7, 2.5, & 3.1, and to those who have worked very hard on the Joomla Platform separation project.
If you are an extension developer, please make sure you subscribe to the general developer mailing list as this is a place where you can discuss extension development and news that may affect custom development will be posted from time to time.
Following is a list of previous news and information about Joomla and other sites of interest:
This beta release is the result of thousands of hours of work by dozens of volunteers. Thank you so very much for making Joomla the best CMS on the planet!
The following bugs have been fixed:
[-] Subscriptions that included mail services were not properly removed from PPA.
[-] PPA removed the main license key when a license key for a service node was terminated by the Parallels licensing system.
[-] Administrators failed to add service nodes because PPA incorrectly selected an IP address for communications between the management node and service nodes.
[-] Administrators failed to back up customer accounts that had Windows-based hosting subscriptions.
[-] The ppa_mssql package was installed successfully, but the database server was not available for use.
[-] Administrators failed to correctly transfer subscriptions with web forwarding configurations from Plesk for Windows. They encountered the following errors in the console: “Error: Failed to work around IIS dedicated application pools problem. Exception: (‘Failed to %s IIS dedicated application pool, see debug log for more details’, ‘enable’)”
[-] Administrators could not transfer customer accounts from Plesk to PPA if the accounts were associated with a single e-mail address. The following error message was shown in the console: ” There are a number of accounts that are associated with the same e-mail. Change e-mails for the conflicting accounts.”
[-] Administrators failed to move subscription between nodes in case the subscription’s domain had the standard forwarding type. PPA raised an error like “Exception message: Command /usr/local/psa/bin/sw-engine-pleskrun with arguments …”.
[-] When transferring a domain alias with the switched off mail service to PPA, the PPA moving tools erroneously registered the alias on the SmarterMail service node.
[-] The PPA moving tools added the content of the default site template to all transferred subdomains. Thus, after the transfer, subdomain’s root directory contained not only its source content but the content of the PPA site template as well. This happened only when perfroming the transfer from Expand based on Plesk 8.
[-] The PPA moving tools failed to transfer subscriptions that belonged to resellers’ customers.
[-] In some cases, the www DNS records were not transferred to PPA from source Plesk Panel servers.
[-] The ppa-transfer tool failed to transfer subscriptions to PPA in case they were associated with the same system user. The tool raised an error like ” [ERROR] parallels.common.safe |copy-content| Failed to perform an action on subscription…”.
[-] The PPA moving tools failed to transfer domains to PPA in case that domains had IPv6 addresses only.
Following check items have been added:
– check for possible business logic issues
– check for broken relationships between tables siteapppackages and apsapplicationitems
The following bugs have been fixed:
[-] Any installation of osTicket APS application is treated by Plesk as global helpdesk. (114056)
[-] (Windows only) Error “Component php5_4 isn’t supported” at subscription creating (131758)
[-] MySQL databases aren’t migrated from Plesk 9 and Plesk 10 if Plesk admin password containing ‘#’ symbol (120651)
[-] Upgrade php component breaks permissions on php sessions directory (91998)
The following new features have been implemented:
[+] Webmail server nodes. Webmail server nodes are now supported. By default, webmail services are provided by the management node. To reduce the load on the management node, administrators can add a webmail server node to the system.
[+] Support for external mail servers. Administrators can add any external mail server to the PPA infrastructure. This may be useful, for example, when you need to use an MTA which is not supported by PPA’s standard mail node roles. The connection with such servers is performed by means of special APS apps, so-called connectors. Such a connector should be developed and registered in PPA before adding an external mail server node.
[+] Login page branding. Administrators and resellers can adjust the appearance of the login page.
[+] Easy changing of the management node’s IP address. Administrators can seamlessly move the management node to another IP address using the /usr/local/ppa/bin/ppa_ipaddress utility.
[+] Support for SNI on branding subscriptions. Administrators and resellers can use unique SSL certificates for brands on shared IP addresses.
[+] Forced retrieval of PPA license keys. Administrators can update the information about their PPA license keys at any time in License & Security > License Manager.
The following functionality have been improved:
[*] Automatic updating of license keys was improved.
[*] Now administrators can limit the number of subdomains on subscriptions.
[*] Administrators can now connect service nodes with CentOS 6.x or RedHat Linux 6.x without needing to preliminarily configure YUM on them.
[*] The migration process was improved: now it is faster and it takes less disk space.
The following bugs have been fixed:
[-] Administrators failed to properly complete the installation of PPA on CentOS 5.8. On attempting to log in to PPA through a web browser, they encountered the “500 Internal Server Error”.
[-] Administrators sometimes failed to connect a service node if (1) they selected two different IP addresses in the node connection settings: one as the backnet IP address (used for communications between service nodes and the management node) and another as the IP address for hosting; and (2) if both IP addresses were from the same subnet range. They encountered the following error in Task Manager: “Can not configure agent on host ‘IP address’, reason: ‘Stopping pleskd: [ OK ].”
[-] Administrators could not create branded subscriptions on dedicated IP addresses. The subscriptions were always created on shared IP addresses.
[-] Administrators could make management nodes inoperable after installing the Apache services. For this reason, PPA no longer allows installing Apache, Postfix and MySQL on management nodes.
[-] Auto-reply messages could not be shown by mail clients due to incorrectly specified MIME type.
[-] Users were unable to host different web content on domains and subdomains that were hosted on the same dedicated IP address.
[-] Users could not calculate the size of a directory in Content Manager. They encountered the following error: “Unable to get size for . System error 13: Permission denied.”
[-] AWStats did not calculate website visits statistics properly.
[-] Administrators failed to create subscriptions with mail services if the mail service was provided by Postfix installed on the management node. They encountered the following error: “Unable to receive setting ‘plesk_mail_service_node_key’.”
[-] License key expiration warnings shown in the Hosting Panel led to a wrong page.
[-] Administrators failed to migrate hosting subscriptions from Plesk for Linux to PPA if at least one SmarterMail service node was connected to PPA.
[-] During migration from Plesk 11.x, the passwords of resellers and customers for access to the Hosting Panel were reset.
[-] Users were unable to switch off mail services for their subscriptions if the services were provided by SmarterMail. The Hosting Panel raised the following error: “Unable to load object of type DSMail with id=127: Mail_Facade->turnOffDomain() failed: Turning domain off is not supported.”
[-] Administrators failed to create subscriptions with Apache and MySQL hosting on a dedicated IP address. They encountered the following error: Error: Database server mysql :3306 does not exist.
[-] The handling of custom ftp.. and www. DNS records was improved.
[-] Migration from Plesk for Linux to PPA could stall due to an internal error.
[-] After migration from Plesk 8 for Linux, applications installed on websites no longer worked because their databases were not migrated.
[-] If CBM was switched on, and a new auxiliary user account with the Accountant role was partially created in the Hosting Panel (the task failed in the process), then after removing that account from the Administration Panel, users will not be able to create an account with the same username again.
[-] During migration from Plesk for Linux 8.6, domains for which hosting was not configured and the Tomcat service was switched off could not be migrated.
[-] MySQL service nodes could not be added if “sa” was used as the database administrator’s username.
[-] Administrators could not migrate domain administrator accounts from Plesk 8.6 if the account information contained non-Latin characters.
The Joomla! Project is pleased to announce the availability of Joomla! CMS 3 Beta1. Community members are asked to download and install the package in order to provide quality assurance for Joomla 3.1. Joomla 3.1 is scheduled for release on or around March 25th, 2013.
Joomla 3 is the latest major release of the Joomla CMS, with Joomla 3.1 the second short term support release in this series. Please note that going from Joomla 3.0 to 3.1 is a one-click upgrade and is NOT a migration. The same is true is for any subsequent versions in the Joomla 3 series. That being said, please do not upgrade any of your production sites to the beta version as beta is ONLY intended for testing.
This is a beta release and not for use on production sites.
Extension developers are encouraged to work with this release in order to prepare extensions for the General Availability release of Joomla 3.1, though there shouldn’t be any backward compatibility issues. Users are encouraged to test the package for issues and to report issues in the Joomla! issue tracker.
Miscellaneous: 28574 – Removed the GeSHi plug-in
Version 2.5 of the Joomla! CMS is a Long Term Support release and support for it will continue until shortly after the release of Joomla 3.5 scheduled for Spring 2014. Joomla 2.5 users do not need to migrate to Joomla 3.0 or 3.1.
Moving to Joomla 3.x from Joomla 2.5 will be a mini-migration not an upgrade, although for the core of Joomla! the migration should be simple. However, it is likely that templates for Joomla 2.5 will need modification to work with Joomla 3 as will many extensions. Always test prior to migrating and consult with the developers of any extensions and templates you use.
Support for Joomla 1.5 ended in April of 2012 and we continued to support it unofficially until the end of 2012 for medium to high priority security issues.
Does that mean your 1.5 site will suddenly stop working? No, your site will continue to work as it always has. However, Joomla’s developers will not be releasing new versions for Joomla 1.5, so you won’t be getting bug fixes or security fixes. For this reason, it’s recommended to migrate from 1.5.
Moving from 2.5 to any Joomla 3 version is relatively simple, since Joomla has made the process easy for newer versions. Unfortunately, moving from 1.5 is not a trivial task. Fortunately, there are two good extensions that make the process easier: jUpgrade and SPUpgrade.
You have a choice of going straight to Joomla 3.0 or going to 2.5 first. Both jUpgrade and SPUpgrade have versions ready for both versions. Please consult with their documentation on how to migrate from Joomla 1.5 to 3.0/2.5.
For most new/migrated sites, the Joomla! 3 series is the preferred series and starting on it avoids a mini-migration from Joomla 2.5 later down the road. Starting on the Joomla 3 series for a new/migrated site, also provides you with longer backward compatible support (with one-click upgrades) than starting a new site on 2.5 right now, because support for 3.x ends in 2016.
There are a variety of ways in which you can get actively involved with Joomla! It doesn’t matter if you are a coder, an integrator, or merely a user of Joomla!. You can contact the Joomla! Community Development Manager, David Hurley, [email protected], to get more information, or if you are ready you can jump right into the Joomla! Bug Squad.
The Joomla Bug Squad is one of the most active teams in the Joomla development process and is always looking for people (not just developers) that can help with sorting bug reports, coding patches and testing solutions. It’s a great way for increasing your working knowledge of Joomla, and also a great way to meet new people from all around the world.
If you are interested, please read about us on the Joomla Wiki and, if you wish to join, email Mark Dexter, one of the Bug Squad co-coordinators.
You can also help Joomla development by thanking those involved in the many areas of the process. Since the release of Joomla 1.6, a whopping 375 issues have been fixed by the JBS. The project also wants to thank all of the people who have taken the time to prepare and submit work to be included in Joomla 1.7, 2.5, & 3.1, and to those who have worked very hard on the Joomla Platform separation project.
If you are an extension developer, please make sure you subscribe to the general developer mailing list as this is a place where you can discuss extension development and news that may affect custom development will be posted from time to time.
Following is a list of previous news and information about Joomla and other sites of interest:
This beta release is the result of thousands of hours of work by dozens of volunteers. Thank you so very much for making Joomla the best CMS on the planet!
The following new functionality has been added:
Following check items have been added:
The March issue of the Joomla Community Magazine is here! Our stories this month:
Adventures in Joomla! Event Planning…, by Dianne Henning
Interview with Andrew Eddie from The Art of Joomla, by John Rampton
IXAPI startup, by Stefan Neculai
Joomla! Facebook Page Hits 100,000 Fans, by John Rampton
Joomla User Group Toronto — The Journey, by Bob Bloom
The 2nd JoomlaDay Switzerland 2013 in Berne, by Roger Perren
The 3rd Joomla! Day India, by Ashwin Date
JoomlaDay Events in April and May 2013, by Jacques Rentzke
Leadership Highlights – February 2013, by Marijke Stuivenberg
Do LESS in Joomla!, by David Hurley
SEO Optimizing Your Joomla Website, by Luke Summerfield
Installing Joomla 3.0 on local host using XAMPP, by Tuan Bui
Joomla! 3.0 Extension Development Series: Writing The Core, by David Hurley
Differences between the Joomla Framework and Joomla Platform, by Matt Thomas
Training Your Clients with Video – Part 3, by Rod Martin
Adding Access Control through Overrides, by Randy Carey
Standing Out in the Stream – Adding Interactive Posts to your Content, by Ruth Cheesley
The Joomla! Project Wants You – March 2013, by Dianne Henning
It Can’t Be Said Often Enough. Save, Update and BackUp Your Site, by Markus Færø-Lunde
Are you Suffering from Keyword Overload? Keeping Google Happy after the Exact Match Domain (EMD) Update, by Ruth Cheesley
Joomla Security Tips 101, by John Rampton
Community Choice Extensions – March 2013, by Peter van Westen
Post your Haikus for March, by Dianne Henning
Browse the international articles submitted this month.
We want to publish your Joomla! story in the next JCM issue! So take a look at our Author Resources content to get a better idea of what we are looking for, and then register to become a JCM author and submit your Joomla! story!
The following checks have been added:
– check that Plesk components used on Source server is installed on Destination server.
The following bug has been fixed:
[-] (Windows only) defpackagemng.exe hangs on if Plesk package DLL info contains double slashes.
[+] (Windows only) MailEnable 7 support has been added. Now MailEnable 7 package included to Plesk distributive.
Plesk Service Team is pleased to introduce the Plesk Webserver Configuration Checker.
The Plesk Webserver Configuration Checker is designed to help in the investigation of problems related to the generation of webserver (Apache/Nginx) configuration files.
Enterprise Monitor product. You can subscribe to RSS or Atom feeds, linked from this page, to
New check has been added to File System section:
– Immutable attribute on Plesk files can interrupt upgrade.
53 queries. 9.5 mb Memory usage. 0.339 seconds.