Jan Zeman

Hi Mike,

It’s been a week by now and there was no any follow up from you. Let me mark this topic as resolved. Naturally I will still be more than happy to reply you here or via email as stated above.

All the best, Jan

Hi Mike,

My apologies for the delayed reply – I was away for a long weekend.

I just did a quick check, and everything looks OK with my albums. Let’s figure out together what might be wrong.

Could you please contact me at jzsa@duck.com? Since we are both Czech, feel free to write in out native language 😉

Best regards,
Jan

Hola @luisbenitez777 ,

I am truly grateful for feedback like yours. It really gives me energy to keep going 🙂

Please download version 2.1.8 and search for fullscreen-mosaic and seven similar parameters 😉

¡Que tengas un día maravilloso y mucha alegría con tu sitio web!

Best regards,
Jan

Hi Naveen,

Thank you for the suggestion. I agree this is a very good idea, and I would like to add something like this in the (hopefully near) future.

At the moment my available time is limited, but I have noted it as a feature request.

Many thanks for sharing.

Kind regards,
Jan

• This reply was modified 3 weeks ago by Jan Zeman.

Hi @naveenbachwani ,

I love seeing those three YESes 🙂

As I mentioned last time, I will continue considering further UX refactoring. I am not fully convinced by the idea of collapsing all samples, because the previews provide a clear visual hint and help “sell” the individual features, but I will definitely consider possible changes.

And… YES… gladly, you will find a small “thank you” in the upcoming version’s readme file 😉

Have a wonderful weekend, Jan

Hi Naveen,

Thank you, that is very helpful.

Your message confirms that shortcode rendering on your actual site pages is fine and that the issue is isolated to the Guide page itself. That distinction is extremely important to me!!!

I have quickly reworked the Guide page so that the previews are no longer loaded eagerly all at once. Instead, they are now loaded progressively, which should make the page much lighter and keep it responsive much earlier. I have just released this as version 2.1.5.

Once you have had a chance to try it, I would really appreciate your feedback on how it behaves on your site:

• Does the Guide page load faster now on your site?
• Does scrolling through the examples feel responsive?
• Is the Clear Cache area now accessible without the previous bottleneck?
• Based on your feedback, I will decide whether any further restructuring is needed in future versions.

Compared to version 1.0, when only slider mode was supported, the number of features has grown significantly, so splitting the Guide into multiple pages or tabs may make sense not only from a performance perspective, but also from a UX perspective.

Best regards, Jan

Hi Naveen,

Thank you for the follow-up.

The Guide page itself is indeed quite heavy. It currently renders around 60 live samples, so even though it works fine on a clean WordPress setup and on mine 3 environments, I believe it may become problematic on some real sites, depending on the hosting, installed plugins, or the general admin-side load. I will try to find a smarter way to render that page so it does not have to do so much work at once.

In the meantime, the most useful test would be this: Could you create a small otherwise empty test page on your own site and place just one or two [jzsa-album] shortcodes there? Then please check whether those shortcodes themselves show any noticeable performance problems on the front end. That will help us separate “the Guide page is too heavy” from “shortcode rendering on this site is slow in general.” So far, this would be the first complaint about the plugin’s performance, but I do not want to underestimate it in any way.

If you want to build your sample in a way that is closer to your site’s final goal, you can also start a TasteWP or similar site within a few minutes, as I did last time. There, the Guide page works as fast as on my own WordPress instances, so it could be a quick way for you to go through the samples and documentation there.

This is a hobby project, so I likely will not have the next release ready before the weekend. At the moment, I expect the next version to become available sometime during the weekend.

Best regards,
Jan

Hi Naveen,

You understood it correctly. To make it clearer, I renamed it to album-cache-refresh while keeping the old name backward compatible. So in your case, you will only need to click the “Clear Album Cache” button.

In the next version (2.1.3), you will also find a “How the cache works” section with an even more detailed description.

Best regards, Jan