H.O.W.D.Y. Media

Hold the phone. It looks like this website has more than one caching system running, and the caching system causing problems is not WP Fastest Cache.

This would explain why the filters aren’t working as well.

The actual culprit is something called WPLatte built in to the AIT Theme’s “Anchor” theme.

My client apparently has a paid copy of WP Fastest Cache, and it was the only caching plugin installed, so made a bad assumption it was WP Fastest Cache.

• This reply was modified 5 years, 1 month ago by H.O.W.D.Y. Media.

Only this page.

You just need to use CSS.

For a recent project, I moved the title below as well as the navigation arrows to be on top of the image and styled completely differently to match the clients needs.

Hmm,

There are countless notifications about array keys not being set. I tried adding conditions to check if the array keys are not existing to use an empty string.

The plugin appeared to work for a minute, but then it came up with the gray box others spoke of.

Definitely this plugin needs some work for it to work with WP 3.6.

I take it back. I’ve set up a testing site and this plugin had no issue whatsoever that I found.

The redirecting loop was being caused by a conflicting plugin (Paid Memberships Pro) which by default forces HTTPS pages to HTTP. In essence HTTPS got the page showing as HTTPS, then PMP redirects to HTTP, and then repeat forever.

If you are having similar issues, I would suggest disabling all plugins and turn them on one by one until you find the culprit for conflict.

Thanks,

I’ve seen Jetpack on a number of my clients’ sites, but never looked in to what it was. I think that will resolve all of my issues.

I’ve used SVN in the past, but forget the details of it. Plus I was using Zend Studio to manage it, but there was a certain issue with something that required doing something like setting a path for it to work properly. I switched to NetBeans, tried it there, but NetBeans (7.0) was being impossible and refused to update or work regarding SVN. I wound up using TortoiseSVN to make things easier.

On the to-do list. There’s poking around being done to move them to assets.

Excellent!

Of course, it is transparent to them, most will never open the folder to see what is inside. I was thinking about factoring concerning WordPress. Most code can fit easily in to a small image, a single screenshot can be several times the size of the code itself, so logically it would be best to make it so these files are not packaged. It would probably cut the bandwidth total from plugin downloads in half at least.

I realize WordPress isn’t hurting for bandwidth, but I come from the days of programming with only 4K of memory, and a large chunk of that is reserved for video and OS (Commodore Vic-20, anyone?). I have learned to code while keeping things concise and just as powerful without unneeded bloat. I miss the days when your OS fit on a floppy or even just within a few megs, but those days are gone now. Still, I persist on making tight code and reducing resource usages.

Ah, eShop simply directs the user to a website to see the screenshots. I prefer having them visible right on the plugin page, so I suppose they will have to endure the burden of a few kilobytes of wasted space.

Oh well.

I’ll have to look in to that as the readme documentation doesn’t mention what syntax is used for adding images.

What about the assets folder? Why can’t the screenshots be kept there if they will be static? I understand that the screenshots may change with each version, but only one set of screenshots will be shown on the WordPress plugin page at any time.

Thanks, that took care of it immediately.

Unfortunately, the guide provided isn’t exactly clear. It would be great if there was a ‘when you are done, it should look like this’ section with a block like the following:

+ branches (empty)
+ tags
  + 1.0
     plugin.php
     readme.txt
     screenshot-1.png (optional)
     screenshot-2.png (optional)
+ trunk
  plugin.php
  readme.txt
  screenshot-1.png (optional)
  screenshot-2.png (optional)

Is there a way to prevent adding the screenshots to the plugin when downloaded? They are wasted space for the end user.