This topic contains 14 reply and 2 voices, and was last updated by towhid 4 years, 2 months ago
Viewing 14 Posts - 1 through 14 (of 14 total)
Author Posts
July 23, 2015 at 8:11 pm 56746
towhid Can anyone explain me the logic of Subscription->"Expires in" and Enable Subscription->"Enable Post Expiration". I couldn't find detailed explanation in help docs. I figured that if Expires in time reached, then subscription pack no longer available, all remaining posts goes; if I enable Post Expiration time, all the posts status changes to post status setting when Post Expiration Time reached. So, what happens if both options enabled or what happens to published posts after "Expires in" time reached. I use empty value in "Expires In" and specified "Post Expiration Time" after enabled "Enable Post Expiration" option. When i use [wpuf_sub_info] shortcode, there is no info about post expiration, page just shows Subscription Name, Package & billing details, Remaining post and Expire date. How could the users learn that their posts will expire, there is no info. You should add information about this. And, there is a bug in .../class/subscription.php line 677: <strong><?php echo _e('Expire date:'); ?></strong> <?php echo wpuf_get_date( $expire ); ?> this line returns actual date if $user_sub['expire'] == 'unlimited' I changed to: <strong><?php echo _e('Expire date:'); ?></strong> <?php echo $expire; ?> to make it work for me.
July 26, 2015 at 10:22 am 58373
towhid towhid

Hello Gökhan,

Post-Expiration feature is not literally included in the subscription package. This two feature is different. Subscription feature will show up in subscription info, what have sets in the subscription form settings.

Thanks

August 1, 2015 at 9:53 pm 64775
Gökhan Aktaş Gökhan Aktaş

Thanks for info, but there are some problems:

When I edit a subscription, only postmeta table is updating in database, _wpuf_subscription_pack in usermetameta table is not affecting. All the information about remaining posts, expire date, package & billing details for a user is storing in usermeta->_wpuf_subscription_pack but the plugin is not changing this data.

This is a very big issue, can you explain me how can i edit a subscription info without affecting any user?

August 3, 2015 at 5:39 pm 65026
towhid towhid

Hello Gökhan,

I have tried to reproduce this issue but failed. It could be a has a chance of theme or plugin conflicts. You can disable all your plugins except User Frontend and switch to a default theme of WordPress like- Twenty Twelve, Twenty Thirteen, Twenty Fourteen and let me know the results.

Thanks

August 3, 2015 at 6:21 pm 65043
Gökhan Aktaş Gökhan Aktaş

I tried, same result. I disabled all plugins and tried with default wordpress theme, nothing changed.

The problem is when you update a subscription pack, it works. But if you update a subscription pack, you have to update all the users subscription info, but your update function is not doing that, it’s just updating the pack. If the problem is on my side it’s OK, we can fix it. But I did not see any action that your subscription update function is updating all the users subscription meta who are using updated subscription pack.

August 4, 2015 at 12:27 pm 65188
towhid towhid

Hello Gökhan,

Can you please provide me an example with some screenshot. A video-cast will be help me to get the bug.

1. A screenshot of created subscription pack in backend.

2. Screenshot of a user assign a particular subscription pack

3. An the user subscription info from frontend.

Thanks

August 4, 2015 at 2:04 pm 65204
Gökhan Aktaş Gökhan Aktaş

This is original free subscription pack I created:
1

This is after update:
2

I deleted:
3

This is subscription info for a user, I uploaded only one because it’s same for all 3 conditions. Changing the post count effects nothing, and yes, after I deleted the subscription pack, the user still shown in a subscription pack that even not exists.
4

August 4, 2015 at 2:07 pm 65205
Gökhan Aktaş Gökhan Aktaş

I tried this for 3 different users, same result.

August 5, 2015 at 3:55 pm 65425
Gökhan Aktaş Gökhan Aktaş

Check this out.
Same problem in your demo site.
Any suggestion?

August 6, 2015 at 4:00 pm 65630
towhid towhid

Hello Gokhan,

I have to reproduce this issue. Please allow me sometimes. Hope I will come back to you with a right solution.

Thanks

August 9, 2015 at 4:48 pm 66126
towhid towhid

Hello Gökhan,

Actually a user will not get the updated package info. Because it means, a user already paid an amount and that amount have reached to a site admin account.

Thanks

August 10, 2015 at 1:22 am 66177
Gökhan Aktaş Gökhan Aktaş

Hello,

If you say that we can’t solve this bug because it needs too much effort, this could be a better support than your answer. Because we bought know that when I update a subscription package, I don’t have to update the price, and we bought know that I can even update a free package, and also we know that if I want to update price of a package that its amount have reached, it’s my problem. You should provide me a working extension.

So please answer if you going to fix this bug, or continue to pretext.

August 11, 2015 at 11:47 am 66448
towhid towhid

Hello Gökhan,

It is not a bug. We do not have this kind of feature. If there is no feature like this then that does not mean- it is a bug.

To avail this kind of addition you have to customize the plugin.

Thanks

August 11, 2015 at 7:03 pm 66567
Gökhan Aktaş Gökhan Aktaş

Let me clarify your answer, in your opinion, if you update wpuf pro and release the update from back-end of wedevs.com, the customers will not get the update from their dashboard, and this will not be a bug. Customers know that the plugin is updated but they can’t install. Because dashboard page is not updating, but this is not a bug. You don’t need to solve this problem because this is not a problem, this is normal.

You say that if users can’t see an updated information that directly associated with them, this is normal, not a bug.
Please give me an example that working like you say.

I don’t have to customize the plugin, you have to solve this bug.

August 13, 2015 at 12:11 pm 66839
towhid towhid

I understand your opinion.

But, we can not provide this feature with default. Because many users do not need this functionality. If they need, they have core code in their bag, they can just extend the code as their requirements and get the job done.

Whatever, We develop an extension or make a feature if there are 15 numbers of request.

Hope you understand.

Thanks

Viewing 14 Posts - 1 through 14 (of 14 total)