B

Forum Replies Created

Viewing 25 posts - 1 through 25 (of 42 total)

B
Participant

Thanks for your swift answer. Yes, I am able to edit out that part of our theme – let’s conclude that this is sufficient for now ๐Ÿ™‚


B
Participant

Hi! I updated to your 5.2.6, and that caused this to happen:


B
Participant

Any updates? We really need to be able to control packages by using categories (and categories have access based on roles).


B
Participant
This reply has been marked as private.

B
Participant

Bump?


B
Participant

As I said, we have customers that fall into mainly two categories; A or B. We have a lot of users, which again are in lots of roles, and their access to A or B may vary over time. That is why we do not want to have “All Visitors” or “Customer role X” as access levels, it is more convenient to make use of access to categories (we can include or exclude roles to categories over time). Roles are then added to a category, and the packages are tagged with said category.

Do you understand?


B
Participant

Thank you for your reply, Nayeem.

The other site is also updated to 5.2.4 now, with the same error. As I said in a previous reply, these packages have access based on categories (and roles have access to categories depending on licences). So no access to users/roles on the specific package, but the package is part of a category that have access rules on roles.

I hope for a quick response again now, and for you to see this as an error that can be fixed (it used to work).


B
Participant

Hi. This is still an issue on the latest 5.2.4 release. Also – incredibly unhappy with no answers the past months. We recently updated our payment for another year of pro, but the support does not seem to have an impact on that.. Can you please answer me and help me with this? We are getting numerous complaints by our customers using our site (and your plugin) because of this..


B
Participant

I have updated to 5.2 pro, and this is still an issue. Please help us!


B
Participant
This reply has been marked as private.

B
Participant
This reply has been marked as private.

B
Participant
This reply has been marked as private.

B
Participant
This reply has been marked as private.

B
Participant
This reply has been marked as private.

B
Participant
This reply has been marked as private.

B
Participant
This reply has been marked as private.

B
Participant
This reply has been marked as private.
in reply to: Sorting by update_date does not work properly #132557

B
Participant

Maybe you can also investigate why some of the download buttons says “blocked” after changing to the newest bootstrap?

in reply to: Sorting by update_date does not work properly #132556

B
Participant

Any updates?

in reply to: Sorting by update_date does not work properly #132335

B
Participant
This reply has been marked as private.
in reply to: Sorting by update_date does not work properly #132330

B
Participant

Hi. This is still not working.

in reply to: Sorting by update_date does not work properly #130334

B
Participant
This reply has been marked as private.
in reply to: Sorting by update_date does not work properly #130096

B
Participant
This reply has been marked as private.
in reply to: Sorting by update_date does not work properly #130080

B
Participant

Hi! Thanks, it works in manual mode now, but the default behaviour from short code still does not work;

[wpdm_all_packages items_per_page="20" categories="stable" jstable=1 cols="page_link,file_count,package_size|version|categories|update_date|download_link" colheads="Title|Version|Categories|Update Date|Download::155px" order_by="update_date"]

It does som random (?) sorting – what is wrong with my shortcode?

I want to default update_date as the order (descending).

in reply to: Sorting by update_date does not work properly #129816

B
Participant
This reply has been marked as private.
Viewing 25 posts - 1 through 25 (of 42 total)