Limitation of images per subscription plan

[mrdanx]

Thanks a lot for your explanation and guidance.

I’ll try to handle the implementation on my own based on what you shared. If I run into any issues or need further clarification, I’ll get back to you.

Thanks again for your support!

Best regards,

[condorito.fr]

Get back to us with your solution buddy !

[mrdanx]

Hi,

Thanks again for your suggestion, I’m moving forward with the “Extra Images” toggle approach.

I’m now wondering how I can access the data entered during the “Add Details” step (listing form) when I reach the “Select Package” step. My goal is to check whether the “Extra Images” toggle was selected, and based on that, dynamically show or hide specific packages.

Is there a way to access the current listing’s data on the package selection page? Or should I temporarily store the listing data (e.g., in the session or database) before the final submission?

Thanks in advance!

[ihor]

Please try adding this checkbox as a custom attribute of Checkbox type in Listings/Attributes. Then you can insert it into the submission form via the hivepress/v1/forms/listing_submit filter hook, this is the easiest way to do this (in this example the attribute is named “extra_images”):

add_filter('hivepress/v1/forms/listing_submit' function($form) {
    $form['fields']['extra_images'] = [
        'label' => 'Extra Images',
        'caption' => 'caption text here',
        'type' => 'checkbox',
        '_order' => 123,
    ];

    return $form;
}, 1000);

Then you can access it anywhere using $listing->has_extra_images() if the listing object is available. Please note that unfortunately we can’t provide further detailed guidance along the custom implementation, I highly recommend using the upcoming Memberships version instead.

Hope this helps

[mrdanx]

Hi,

Thanks for the explanation and the example! I’ll try to build on this approach and see how far I can go with it.

If I run into any major issues, I’ll get back to you.

Thanks again for your help!

Best regards,

[mrdanx]

Hi,

Just to make sure I understand correctly:
There’s no direct link between the listing submission (“Add Details”) and the package selection (“Select Package”) steps — at least not in a way that would allow me to easily access the data entered in the form just before.

So if I want to check whether the “Extra Images” checkbox was selected before showing the packages, I would need to pass the listing ID to the package selection page somehow — either through a URL parameter or by storing it temporarily (e.g., in the session or a transient).

Without that ID, it seems there’s no way to know what was submitted during the previous step.

Let me know if I’m missing something here.

Thanks again!

[mrdanx]

Hi,

I’m currently rethinking the way I want to handle monetization on my site, and I’d like to share my thoughts here to get your opinion.

Initially, I planned to use the Paid Listings extension, with different packages allowing various features (number of images, featured status, etc.). However, after digging into the logic and trying to implement dynamic options (like showing/hiding packages based on fields in the listing form), I’m starting to feel that this might not be the most flexible solution in the long term.

I’m now considering skipping the package selection step entirely, and instead redirecting users to a WooCommerce product page, where they can choose the desired paid options — such as “extra images”, “featured listing”, etc. These products would be created manually in WooCommerce and used as modular add-ons for listings.

I would then use custom hooks to apply the selected options to the submitted listing (e.g., mark it as featured, extend the number of allowed images, etc.).

From a technical point of view, is it possible to redirect the user to a WooCommerce product page immediately after the listing submission, instead of showing the default “Select Package” step from the Paid Listings extension?

Thanks in advance for your feedback!

[ihor]

Hi,

This would require more complex customizations, if Paid Listings are still needed along with redirection to WooCommerce products, because skipping the Select Package page may be tricky (after WooCommerce products are purchased). If you want to proceed with this solution, I recommend starting by replacing the “redirect” function of Select Package page by adding a function to the hivepress/v1/routes hook and replacing the “redirect” parameter of the “listing_submit_package_page” route so it points to your own custom function. You can check how the default redirect function is implemented here hivepress-paid-listings/includes/controllers/class-listing-package.php at master · hivepress/hivepress-paid-listings · GitHub Regarding the listing ID question, you can always get the listing object within the listing submission process this way:

$listing = hivepress()->request->get_context( 'listing' );

Hope this helps

[mrdanx]

Hi,

Thanks a lot for the clarification and the details about the internal redirect logic.

After reviewing the complexity involved in overriding the “Select Package” step while keeping the Paid Listings extension active, I’m leaning toward not using the Paid Listings extension at all. My goal is to simplify the submission flow and have full control over the monetization options.

By relying solely on WooCommerce products (created manually), I believe the overall logic will be more flexible and easier to maintain — especially as I want to offer individual paid options like “extra images” or “featured listing” independently.

This approach would allow me to:

• Keep the submission form simple.
• Redirect users after submission to a custom WooCommerce page with the available paid options.
• Handle everything (feature activation, image limits, etc.) using hooks and WooCommerce order status.

Do you think this is a clean and viable approach from a HivePress perspective?
Any potential limitations I should be aware of before going down this route?

Thanks again for your support!

[ihor]

The approach with redirecting to WooCommerce product may work (if you decide to implement this, please check how Paid Listings add a custom step to the Add Listing process, via the hivepress/v1/menus/listing_submit hook, you can also browse the full Paid Listing code on GitHub), but this would be similar to implementing the whole (but simplified) Paid Listings logic from scratch.

I recommend using the upcoming Memberships version (it’s scheduled to be released tomorrow) - it will show packages before the Add Details step so you will be able to add 2 packages like “Basic Listing” and “Detailed Listing” (and describe the benefits like extra images, etc).

[mrdanx]

Hi,

Thanks for your reply and for the heads-up regarding the Memberships extension — good to know it’s coming so soon!

I understand that building a custom WooCommerce-based flow would mean essentially recreating the logic of Paid Listings in a more modular and manual way. While it gives me full control, it also involves maintaining the whole integration, which I’m aware can become quite complex.

That said, my main goal is to keep the user experience as clear as possible and to have full flexibility over the monetization logic (extra images, promotions, category-specific rules, etc.). I’ll take a look at the Memberships version when it’s released and see if it could simplify things while keeping that level of flexibility.

Thanks again for your great support!