reinhardf
Forum Replies Created
-
@alex
You can not say only 100 of 10,000 updates do not work. The errors since version 2.0.0 are so many that EVERYONE is affected. Some just do not notice it immediately or have not yet been updated. While others might have been updated and tested ten times unsuccessfully and downgrading. So 10,000 downloads could possibly be carried out by 2,000 users.In my opinion it is ok that a free plugin does not work right for some users after a big update.
But it is not ok if your entire site therefore no longer works even without any plugin conflicts. And it’s not OK, that at a photo plugin that you delete all photos are deleted. It is surely clear that one wants to keep his uploaded photos!
Some write the source code quality is very good. but if you look here:
https://bitbucket.org/photocrati/nextgen-gallery/commits/all
the programming is rather sloppy and confused. They make new versions without testing it properly. This can be seen in the time column.
Also suggests that photocrati is overwhelmed:
“124 of 997 threads in the support load two months have been resolved.”Version 2 was too much. So many changes makes one better in small increments. But they wanted their PRO version just sell quickly. Think about: They want $ 39 per year – that’s $ 390 in ten years!
Forum: Reviews
In reply to: [Photo Gallery, Sliders, Proofing and Themes - NextGEN Gallery] 2.0 killed itYes – Version 2.0 is a load of crap!
Very annoying. I warn everyone to make an updatedouble post ??
Hi Tom,
I think google page speed still nags, both at 1 and at 3 imports. But these small mistakes cost you no speed points. So it does not matter much. It will probably be the best html5 valid solution at the moment.
Thank you for your work on the free plugin and your great support.
So with new version 2.1.5: Topic resolved.Hi Tom,
I’ve just tested the version 2.1.5.
For me it’s ok. Small warnings at Google Page Speed??, Ok at GTMetrix & PingdomTools. But strangely enough, just HTML5 valid. ??Hi tom,
many thanks for the explanation. The html 5 validation problem is not so important. Your slider is great – I will test W3-Total-Cache later.
Hi Tom,
for your info:
Version 2.1.2 (HTML5 Validation fix for inline styles) shows the same HTML5-Validation-errors.Example (here Version 2.01): https://validator.w3.org/check?uri=https://www.matchalabs.com – last three errors: “Element link is missing required attribute property.” because CSS in footer.
Same problem: https://www.ads-software.com/support/topic/slider-not-appearing-with-js-css?replies=7
My Solution:
I’ve just unchecked printcss.
And in header.php (<head>-area) i’ve added the 3 css-lines:
<?php
if ( is_page (‘home’) ) {?>
<link rel=’stylesheet’ id=’metaslider-display-css-css’ href=’…/wp-content/plugins/ml-slider/assets/metaslider/public.css?ver=2.1.1′ type=’text/css’ media=’all’ />
<link rel=’stylesheet’ id=’metaslider-nivo-slider-css-css’ href=’…/wp-content/plugins/ml-slider/assets/sliders/nivoslider/nivo-slider.css?ver=3.5.1′ type=’text/css’ media=’all’ />
<link rel=’stylesheet’ id=’ml-slider_nivo_slider_theme_default-css’ href=’…/wp-content/plugins/ml-slider/assets/sliders/nivoslider/themes/default/default.css?ver=3.5.1′ type=’text/css’ media=’all’ />
<?php }?>hi tom,
thx
that would be great if this works html5-compliant. Eliminates manual intervention when plugin updates. ??
### I may take these options out of the next release). ###
I’ve also unchecked printcss.
Unfortunately, this (load CSS in footer) is not html5 compliant. <link> CSS instructions must be in <head> area. (Only JS should be loaded in the footer.)