Erick Danzer

Hey @soniagon – If you’re looking for a refund on the Pro version of the plugin, you should reach out on the plugin site at https://firelightwp.com/contact? The forums are just for the free version.

• This reply was modified 6 days, 7 hours ago by Erick Danzer.

Hi @bradthebluefish –

Are you displaying your category / taxonomy terms as part of a filter? Or are you trying to simply display and ajax loaded / infinite-scroll-style list of categories / terms?

For now, I assume it’s the first. If so, I’m also wondering if you’re already using the ALM Filters add-on?

If you are, and you’re displaying a category-based filters, you are right that will normally filter out empty categories. You can you prevent it by doing so by setting ‘hide_empty’ => false as a custom arg. But to do that, you’ll need to use the custom alm_filters_[id]_[key] filter. Docs for that are here: https://connekthq.com/plugins/ajax-load-more/docs/add-ons/filters/hooks/

But a simple example might look like this, assuming I’ve created a filter called ‘my_filter’ and I’m filtering by category.

add_filter( 'alm_filters_my_filter_category', function() {
  $values = []; // Define empty array.
  $args = array(
    'hide_empty' => false
  );

  $terms = get_categories($args); // Get all categories.

  // Loop terms.
  if($terms){
    foreach( $terms as $term ) {
      $values[] = array(
        'label' => $term->name,
        'value' => $term->slug
      );
    }
  }

  return $values; // Return values
});

Hi – How are you creating / storing your chapters? Are they stores as separate posts / post types?

Whatever they are, the process loading them via AJAX would be the same as other types of content:

1. Create a repeater template. This is just a code snippet that renders markup for a single instance of whatever you’re displaying – in your case a single chapter. It might have an image, the chapter title, an excerpt, etc.
2. Build a query (and shortcode). ALM has a very easy interface for this. But say your chapters are posts types, or are posts with a particular category. Just create a query that pulls in all those chapters. You can set how many you want to show. You can set if you want more to show on scroll or by clicking a button.
3. Add the shortcode. Just go to whatever page or post you want to use to display your list of chapters, and insert the shortcode. There’s an ALM block for this if you are using the code editor.

For Elementor, the only real change is with #3. You’d just insert the ALM shortcode using an Elementor shortcode widget.

We have great documentation, and for more details on each of the steps above, please see this page:
https://connekthq.com/plugins/ajax-load-more/docs/implementation-guide/

Let us know if you have other specific questions.

I was working on some small changes and decided to just make the webp change and push a small release. If you get a chance, please confirm webp is working as you’d expect. Thanks!

By the way, if you have any other outstanding feedback or suggestions please feel free to share. As a new maintainer, I’m very interested right now in hearing feedback or suggestions from those who have been actively using the plugin.

Hey there @i0n1ca! After an amazing, long run by @ulfben, I’ve taken over the maintenance of this plugin. I intend to continue actively supporting it indefinitely. I’ll be posting some kind of announcement soon, at least here in the forums.

I’ll happily include your change in the next release, hopefully within the next 1-2 weeks. Thanks very much for following up on this change, and for the detailed code suggestion/fix – even with line numbers :).

@crimsonmed – Thanks for coming back and providing the extra input. It may still be a plugin conflict on your site, but we’ll make an effort to check against Hitcock.

Given the symptoms your describing, and how uncommon they are for NG users, it seems fairly clear you’re experience a theme or plugin conflict. While that’s quite rare these days, it can still be hard to ensure compatibility with all of tens of thousands of plugins and themes out there.

If you feel motivated enough to troubleshoot, the way to find a conflict is to:

1) Deactivate other plugins one by one OR deactivate all plugins and reactivate one by one. If you do this, you’ll find one particular plugin that triggers the issue.

2) If you go through #2 and don’t find any issues, it’s likely the theme. You can test by changing themes, but most users prefer not to do that. Alternatively, if you have a second WP instance, you can test there. I’d even say that if you go through the process for #1 and don’t find an issue, you can just let us know what theme you’re using, and we’ll test ourselves.

Otherwise, I assume you’ll move on. We appreciate you giving the plugin a try. Sorry it’s not working for you. We hope you find a great solution that does.

Hi @suwarrow9. Thanks for taking the time to review. NextGEN Gallery is free. Can you clarify what you mean by ‘too expensive’?

@arthughesphoto – Sorry to read this. Sounds like you had some bumps. Based on your experience, seems like the review in your case was warranted.

I did want to clarify – from past topics you’ve posted it seems like you were using NGG as long a 4 years ago. Did you go away and just come back, or were you using it for that long, and just had problems more recently?

–

For others who may read this, the experience here is obviously not typical or common as you can see from other reviews. I’m assuming something was just not agreeing between NGG and this users hosting environment or WordPress set up. That’s not to diminish this user’s experience. As stable as NGG is, it can be hard to keep it perfectly stable in each of hundreds of thousands of environments none of which we control. That’s a challenge for all popular plugins.

–
Again, thanks for taking the time to share the feedback.

Thanks for taking the time to leave a review. We’re wondering if you can clarify.

You said “when I delete the plugin I see error messages.” But if you delete the plugin, by definition, the plugin’s code is no longer present anywhere on your site, and thus cannot generate any errors.

The only thing we can think here is that you’d inserted a NG gallery, then later removed the plugin, and you’re seeing something the lingering shortcode where you’d previously inserted your gallery.

It might help if you post the actual error message if you’re willing.

Thanks.

@tommuc1 – Unless I’m misunderstanding your request, I’d think you could just use a media query for that. The following code for example would only hide the caption on screens smaller than 600px:

@media only screen and (max-width: 600px) {
  .sl-caption {
    display: none !important;
  }
}

You can obviously change the 600px there up or down depending on whether you want to target just phones, or include tablets too.

• This reply was modified 5 years ago by Erick Danzer.

@adpassion – Hi! I just wanted to let you know that you can use NextGEN Gallery with WPBakery, you just need to use shortcodes. Go to any normal page or post, use the default NGG interface to insert a gallery, then in text/html view, grab the short code. Insert that shortcode via any relevant method into a WPBakery page (or for other page builders), and it’ll work.

We just tested and confirmed to be sure.

It is true that NextGEN Gallery’s Insert Gallery Window doesn’t work with WPBakery or some other page builders. The reason for that is simple – NGG’s insert gallery UI interface is built to work with the WordPress editor, either classic or block version, not with the custom editors provided by many page builders. We’d have to build a custom version of NextGEN’s insert gallery interface for WPBakery and each other page builder to make that work.

And for now, it’ll still work just fine to use insert a NGG gallery via shortcode.

Would that work for you?

Please let us know if you have other questions or issues.

Hi @gwatuk – Thanks! I just wanted to add a few quick notes to manage expectations.

* As of now, we don’t have any concrete plans to add an option of this kind.
* This is a feature request, and it’s a decent one. But we have hundreds (maybe thousands) of feature requests from hundreds of thousands of users. We typically triage feature requests, and pursue those that will have the biggest impact for the largest number of users. It’s always a hard call. Some features – like Print Lab Integration, just released – take years in development.
* Another consideration we always have in our minds: NextGEN Gallery is often criticized for having TOO many options already. It is more options rich than any other gallery plugin. I mentioned we probably have thousands of feature requests. If we added every option that’s requested, our UI would become completely overwhelming. In other words, there is an incremental UI cost to every new option. It’s not a big deal for each one, as we’re discussing here. But it is a big deal if you account for requests by hundreds of thousands of users. So we now think hard about each new option we add.
* In the case of this request, the original poster’s needs were met, for the most part, with some fairly simple custom css. That means for this option, unlike many others, there is a fairly simple work around. Yes, its limited – you can’t customize by image, but it’s worth noting that if we did add an option like this, we’d probably still add it at the lightbox level, not the image level, because that would cover the majority of needs for this, and because it means adding one option, rather than an option for every image in NextGEN Gallery. So even with the option, you wouldn’t be able to customize by image.
* I’d note that we have never added any built-in options to customize the default/free lightboxes in NextGEN Gallery, much less options to customize how each image in a Lightbox works.
* I’d also note that the Pro Lightbox DOES come with dozens of customization options. So there’s already a pro option with similar functionality to what’s being requested here.

Finally, I’ll just add a caveat. We’re never fixed/unmovable on these kinds of discussion. How we evaluate the relative priority and value of any feature request changes over time as we hear from users. If we get enough critical mass requesting – and particularly if we come to sense that this option would be used by a large percentage of our users – we’d elevate its priority and consider adding it and adding it sooner.

I’ll take your feedback here as a strong vote in favor. Same for others of you in this thread. While we’re not yet taking action, I do want to emphasize how much we appreciate that you and others are leaving the feedback. It takes time to come back here and do so. And ultimately, it’ll move the needle if we get enough of it. We’re just not there yet when we take into account the entire picture of our user base and their needs.

I know you still may not be happy that we’re not taking action. But hopefully the context I’m providing gives you a window into why it’s not necessarily an easy or straightforward decision. Thanks and best.

Hi @martinstkonvis – appreciate your security consciousness, but as has been noted, a fix was already available when GoDaddy took this action. That means all that was needed was an update. So GD could have emailed users to update or, if they considered it severe enough, force updated the plugin. For many reasons, this is what almost all hosts actually do in such circumstances.

If GoDaddy is going to delete every thing that has a security vulnerability in its recent changelog, it would need to delete a vast array of plugins, themes, and WordPress itself (WordPress alone has had 11 vulnerabilities in 2019 and 38 sql injection vulnerabilities over its history).

As a side note, this particular vulnerability required admin access. While all vulnerabilities should be treated seriously, it’s still worth noting that once someone has admin access to a website, they can pretty much do what they want anyways.

So based on both the specifics of this case and on industry standards for similar situations, I think it’s fair to conclude that this was a poor and unusual approach on GD’s part.