charleston-wordpress-maintenance-plans

We have some exciting changes to announce at tangerinemoons! As of April 1, 2019, we’ll be upgrading our WordPress maintenance plans to further secure and monitor your WordPress website!

With the daily occurrence of website hacking and programming vulnerabilities, security is extremely important for every website owner. Every day, we see attempts on the sites we maintain by hackers trying to gain access. With this in mind, we have introduced our security threat monitoring, detection and malware removal to ALL of our maintenance plans. See below for further details.

Basic Maintenance and Support Plan is now Lite Plan.

Great for bloggers and personal websites that only need the essentials: security, backups and updates.

Standard Maintenance and Support Plan remains Standard Plan.

Perfect for websites with requirements beyond the basics, including website availability checks. We’ve added 30 minutes of content changes to the existing plan in addition to detailed monthly reporting for backups, maintenance and security.

Premium Maintenance and Support Plan remains Premium Plan.

Perfect for websites with requirements beyond the Standard Plan, including monthly database optimization, performance checks and more frequent offsite backups. Increase in monthly support from 1 hour to 2 hours.

Pro Maintenance and Support Plan remains Pro Plan.

Even more monthly support! An increase from 2 hours to 3 hours make this plan essential for robust, complex websites.

Visit our WordPress Maintenance Plans page for further details on the features and pricing for our plans.

Are you a current tangerinemoons client?

The new maintenance plan changes will not affect your current subscription. New features will automatically be added to your current plan without an increase in the current monthly rate.

Whether you’re thinking about signing up for one of our WordPress maintenance plans or have been a client for years, we appreciate your business and look forward to a lasting relationship, as we work hard to protect and ensure the success of your WordPress website.

For some reason over the past 2 or 3 weeks, when sharing posts from my music blog at arcadianforest.com to Facebook, the shared post would not display the correct thumbnail assigned to the post. I’m not sure if they have changed things up over at Facebook or what the issue was, but I dove into the issue to try and figure out the problem.

First step – I verified through looking at the code that all of my Facebook Open Graph Meta tags were in place and I ensured the thumbnails were at a required minimum of 200px by 200px. The recommended size is 1500px x 1500px but I’m not sacrificing 2 Mb (in this particular case) just to have my post image displayed on Facebook. The Facebook Open Graph Meta tags can be entered into the <head> of the page, or in my case with a WordPress blog, I opted to use a plugin to enter the meta tags based on my blog post. I’m still experimenting with several plugins in providing the best results without loading other unnecessary junk included with the plugin.

Second step – after verifying my image size and tags were in place, I began using the Facebook Debugger tool with several of my posts for troubleshooting and received various results, even with the same plugin and with the same image size. In some cases, the post would check out OK, while in other cases, the tool would tell me that the image was too small.

To make a long story short, I found that it makes a difference in how the file was being saved from PhotoShop (or not). To test this, I took a post that I tested with the FB Debugger tool and told me that the image was too small. I saved the image from the post, opened it in PhotoShop and used the “Save for web” option at 100% optimized, uploaded the new version, inserted the new image into the post and rechecked the same post with the new image and now the post checked out OK.

I also tested by downloading an online image temporarily – then of course deleted the image after testing due to copyright issues ;-) – used the image in a post and FB debugged it, and received the “too small” error message. I opened the same image in PhotoShop, resaved it, uploaded and add it to the post, redebugged it and it checked out OK.

In both cases, I reconfirmed that the thumbnail was working properly by posting on Facebook to see if the thumbnail appeared and after saving the file in Photoshop, and reuploading, they did in each case I tested.

Hope this troubleshooting information will help someone that may run into the same issue … and frustration.

 

 

If you’re anything like me, a cluttered desktop drives you crazy. I can’t stand seeing files and icons everywhere, so I decided to clean things up. The first place I started was the Dock, because I had icons spread all across it.

Step 1: Create folders for your apps
In the Applications folder, I made new folders based on the types of apps I use. My categories were Media, Browsers, Microsoft Office, Creative Suite, and Tools. Then I created aliases for each app and placed them in the right folder.

Some examples:

Media: iTunes, FaceTime, Spotify, Image Capture
Browsers: Chrome, Firefox, Opera, Safari
Microsoft Office: Word, Outlook, Excel
Creative Suite: Photoshop, Illustrator
Tools: Grab, Calculator, Evernote, Jing

Step 2: Add the folders to your Dock
Once the folders were ready, I dragged each one from Finder to the right side of the Dock, near the trash. Be careful not to drop them in the trash.

Step 3: Choose how the folder displays
Right-click the new folder icon in the Dock to choose how it looks. You can pick Fan, Grid, List, or Automatic. I prefer Grid because it makes each app easy to spot.

At first, though, the Dock looked messy again. Each folder showed a stack of app icons, and it made things feel cluttered. To fix that, I created my own simple icons for each category.

Step 4: Create and apply custom icons
I designed my icons as PNG files so they would have transparent backgrounds. Then I used an online tool called iConvert Icons to convert the PNG files into ICNS files.

Next, I went to Finder > Applications, found the category folders I created earlier, right-clicked each one, and selected Get Info.

Open your new ICNS file, copy the icon (Command+C), click the small blue folder icon at the top-left of the Get Info window, and paste (Command+V). Your Mac may ask for your password when you change the icon.

Once the icon is replaced, close the window. Your new icon should now appear in Finder and in the Dock. If it does not show correctly in the Dock, right-click the folder in the Dock and select Folder under “Display As” instead of Stack.

And voilà — a clean, organized Dock without the clutter.

I received three notifications last evening from Facebook regarding changes that are required for three special Facebook app pages I have created. However, it doesn’t seem the changes required were really addressed within the email or the Facebook information page.

Here is a copy of the email:

Hi Larry,
Your app, **********, needs to be updated for the February 2013 Breaking Changes.
Once your app is compliant, set the migration setting to “Enabled” in the Advanced section of the App Dashboard.
These changes will be permanently enabled for all apps in 1 day on Tuesday, February 5, 2013.
You can view this and other Developer Notifications related your app, Welcome, in the App Dashboard.
Thanks,
The Facebook Team

I just love (I’m being sarcastic) how Facebook gives you only a 24 hours notice to the upcoming changes.

It turns out after reviewing the app and comparing the other apps I had setup, the only difference was that they still had the Page Tab Width set to the old 510px instead of the new 810px. This setting may be found under the Basic page of the app under the “Page Tab” heading.

After selecting the 810px width, I visited the Advanced tab and selected the Enabled radio button from the “February 2013 Breaking Changes” option and selected Save Changes and immediately received a confirmation email stating that the app was now compliant with the Feb 201 Breaking Changes migration.