gregl7

@jaimeimagely I haven’t been a paid member for a year or two, as it occurred to me the only time I ever need support is when Imagely releases its constantly buggy updates and breaks my website. So you’re constantly releasing buggy updates that break otherwise functioning websites, and then want customers to pay $100+ a year to troubleshoot issues which Imagely broke to begin with. I have spent countless hours over the years trying to “fix” things that Imagely broke with their updates, including, when I did pay for support, being told issues weren’t bugs, only to find out later they were. The only reason Imagely is still in business is because you’ve got a bunch of photographers being held hostage whose entire websites are based around your buggy software. Over half the issues that are reported on this forum are never responded to and are ignored. The whole thing is a scam. If your developers would get it together and stop releasing bug-ridden updates constantly, and the paid support improved, you might have better luck getting people to pay.

I’m also getting this error on one of my gallery pages in addition to the two I listed above:

Notice: Undefined index: disable_pagination in /home/gleeshot/public_html/wp-content/plugins/nextgen-gallery-pro/modules/nextgen_pro_thumbnail_grid/package.module.nextgen_pro_thumbnail_grid.php on line 56

I originally marked this as “resolved” before looking at my entire website.

After looking at more of my gallery pages, I realized that what I had said above only resolved it when my galleries were set to display as “pro tile”. When they’re set to display as “pro thumbnail grid”, the share icons appear, but at the top of every page these 2 errors appear:

Notice: Undefined index: thumbnail_quality in /home/gleeshot/public_html/wp-content/plugins/nextgen-gallery-pro/modules/nextgen_pro_thumbnail_grid/package.module.nextgen_pro_thumbnail_grid.php on line 37

Notice: Undefined index: thumbnail_watermark in /home/gleeshot/public_html/wp-content/plugins/nextgen-gallery-pro/modules/nextgen_pro_thumbnail_grid/package.module.nextgen_pro_thumbnail_grid.php on line 43

It’s the same line numbers (37 and 43) for every pro-thumbnail gallery. I’ve figured out that this error is appearing when Font Awesome is installed. I had to uninstall the Font Awesome plugin to get it to go away. So for now I’m disabling the share icons as apparently a bug was introduced in a recent version that’s caused the share icons to malfunction and not appear correctly, and installing Font Awesome only puts those errors on the top of certain galleries and makes things worse.

Update to the above: Those 2 errors keep randomly appearing even after uninstalling Font Awesome, so it may be totally unrelated. Starting a new support topic for those 2 errors.

• This reply was modified 6 months, 1 week ago by gregl7.
• This reply was modified 6 months, 1 week ago by gregl7.

Changing the “fontawesome” setting to “yes” made all the icons disappear. But installing Font Awesome and leaving the setting at “no” solved the issue for some galleries, while breaking others. See update below.

• This reply was modified 6 months, 1 week ago by gregl7.

I only found one other post about this on here (https://www.ads-software.com/support/topic/with-the-update-it-does-not-allow-you-to-edit-gallery-sort-or-exclude-images/), which the support department never gave a final answer to — and that was a month ago. Support was talking about “opcache” in that thread, but I disabled it on my website to troubleshoot, and it did nothing. Deactivating and reinstalling the plugin (which is the default answer constantly every time I contact support) did nothing either.

The only reason I — and I assume most others — are still using this buggy plugin is because we have websites with tons of images built around it. When I first started using it several years ago the support was reliable, knowledgeable, and they weren’t continuously releasing buggy updates. For the past 2 years or so, it’s been nothing but headaches with all their buggy releases. I have wasted countless hours troubleshooting their buggy software. Trying to get them to admit there’s a bug is like pulling teeth because they apparently test these updates on only about 5 computers in their office, determine it’s fine, release it it to hundreds/thousands of people, reluctantly discover it’s bug-ridden (after telling everyone to “delete and reinstall the plugin”), and then we have to wait weeks and months for them to fix everything….only to have it happen all over again the next time an update is released. It’s completely ridiculous. If any mainstream software company functioned this way they’d be bankrupt in 6 months.

I also just discovered that if I delete the nextgen block from the page, and then add it back in and connect the gallery, all the images will show up again on the “sort or exclude” screen. But if I then insert the gallery, save the page, and go back into it, the images once again won’t show up on “sort or exclude”. Clearly this is a bug.

Apparently the blank page showing instead of 403 is a Firefox thing, as other browsers I’ve tested actually show the 403 page when I run the eval command.

I mentioned ModSecurity; whenever eval is run ModSecurity pops up with a warning in the error logs. It looks like more of a warning however than actually blocking what BBQ is doing since I get the 403 page:
——————————————————-
ModSecurity: Warning. Pattern match “(?i)\\\\b(?:s(?:e(?:t(?:_(?:e(?:xception|rror)_handler|magic_quotes_runtime|include_path)|defaultstub)|ssion_s(?:et_save_handler|tart))|qlite_(?:(?:(?:unbuffered|single|array)_)?query|create_(?:aggregate|function)|p?open|exec)|tr(?:eam_(?:context_create| …” at REQUEST_FILENAME. [file “/etc/apache2/conf.d/modsec_vendor_configs/imunify360-full-apache/001_i360_1_generic.conf”] [line “24”] [id “77134463”] [msg “IM360 WAF: PHP Injection Attack: High-Risk PHP Function Call Found||T:APACHE||MVN:REQUEST_FILENAME||MV:/eval()||SC:/home/gleeshot/public_html/eval()”] [severity “NOTICE”] [tag “service_o”] [tag “service_i360”] [tag “noshow”] [hostname “gleeshots.com”] [uri “/eval()”] [unique_id “YOtGYD01d2O1rsQVHTgX4gAAAxg”]`

——————————————–

If I disable BBQ and run eval, I get the 404 page instead, which I would assume then means BBQ is working.

Having said all that, if BBQ is working, what is it supposed to be doing when all these random bot attacks take place and my entire site is being scanned? Thanks.