Recent content by Chad Reitsma

That sounds good - but it seems like Plesk is downloading the actual favicon images (.png or .jpgs) from sites that have them - specifically all of our Wordpress sites. Of course we try to optimize them, but Wordpress recommends a 500x500px image and those are generally around 25-80kb each...

We're still keeping them disabled, they don't improve the UX for us.

Thank goodness we can disable this. Honestly, this does nothing for UX and is more of an annoyance/burden on the server. When hosting over 50+ domains, you can see how slow it is as it tries to load the favicons for each domain. Maybe you guys could employ a cache mechanism if it's going...

Here's how I fixed it. 1. Switch to Comodo (Free)(Gratuit) 2. Login via SSH/Console # touch /var/awp/etc/config # aum -u # ln -s /var/awp/bin/aum /var/asl/bin/aum 3. Switch back to Atomic Standard

Hey Brian, Not sure if you saw this article - seems to be an issue with Atomic...

Thanks Rasp, I don't think it's a bug - I just wanted to create this post to help any novice devs. It might confuse them because the code is technically sound, it's just running with a different config.

Thanks Peter! I thought about that too. Where does Plesk store the php.ini for each domain?

Hey guys, I ran into a weird issue when using a scheduled task on one of our client's Wordpress installations. Some background information: The scheduled task is set up as "Run a PHP Script" without arguments. We have changed the 'Access to the server over SSH' to /usr/bin/bash PHP Options -...

Hi guys, It looks like you have coded the Wordpress toolkit to look for files in the installation directory and fail if any files are found - from an Admin level this is simply not good practice. We have several files in our skeleton directory that need to be present when a domain is created...