Forum Replies Created
-
Posts
-
Ciao Alessandro,
l’avevo un attimo lasciato in sospeso per eventualmente raggrupparlo insieme ad altre aggiunte in un unico aggiornamento. Tuttavia non ho null’altro in programma quindi tra oggi e domani lo rilascio, scusa!Oh right, but that is a different problem now. It sometimes does happen, and I honestly have no clue why, but it can be solved by deactivating the plugin, updating it, and reactivating it. The notice should vanish! 🙂
Can you please try to update the plugins NOT from the plugins page, but from Dashboard > Update? Select only one of our plugins and click the update button. If it fails, it should provide some more information on WHY it failed 🙂
Thanks!Ciao Alessandro,
hai ragione, dovrebbe essere presente anche “Sempre” nelle scelte, sarà mia cura aggiungerlo nella prossima versione. Ugualmente per la traduzione di “All time” (che già è presente nel plugin, ma sfortunatamente in altri luoghi è scritto con la T maiuscola “All Time” e c’è un conflitto nelle traduzioni. Se vuoi questo lo puoi già fare (sarà incluso nel prossimo aggiornamento): la riga 86 di post-pay-counter-pro/ppcp_shortcode_class.php, sostituiscila con
$time_range_text = __( 'All Time', 'post-pay-counter' );Buona giornata,
StefanoVersion 1.5.4 of Request Payment solves the non-responsive button issue. If not through the automatic update, you may download the new package through the same link in your email 🙂
So, yes, it would be great that the download link would not be restricted because only the people who receive the email should be able to download it.
Yes, but then you should also think that this software is public, so not only your users would be able to use that link, but also other people would be able to craft an apt URL and see your stats. That is what I was trying to get across in my previous reply, and why login is required even for csv stats 🙂
I am currently having problems with one user’s stats, that shows zero on the front end, but shows correctly if I assign these posts to admin and visit the frontend
Are you maybe creating those posts as duplicates from others, or are they completely brand new posts? Could you try creating a fully new post and seeing if that post gets stats correctly?
send me the latest updated version of buddypress, post pay counter pro and request payment so that I can manually install them. (dewlonse@yahoo.com) my subscription is still active.
Just done! 🙂
check the this link for the issue with request payment not being responsive: https://storage.googleapis.com/stacob/2020/01/88975b83-request-payment-not-responsive.jpg
Thanks for the screen! I’ll see what we can do about that 🙂
Have a nice day,
StefanoHi Chris,
we do not allow that as it would allow even outsiders to download the stats, unless we generated and stored a token for each stats and user, which would clutter the database and I would be against. We could have a custom development where the stats are downloadable even without login, but we would still require some kind of authentication, either through a cookie header in the request, or something similar. Not sure if this helps though! Let me know 🙂Have a nice day,
StefanoHi Charles,
1. What error do you get exactly? Try to update from the WP pageUpdatefound in the Admin Dashboard, and not the plugins page. The Update page does provide some more info.
2. Can you post a screenshot? Does it happen with all mobile browsers for you? 🙂Have a nice day,
StefanoHey,
so sorry for the delay: I did not get a notification for your last reply on the 6th of January and did not try again! I just did so, and fixed the issue 🙂The problem was that you had the option
Require at least # visits to qualify for (any) paymentset to1999(see attached screenshot), but no posts were above that threshold. Thus, any payment was withheld. I changed that to zero and all payments show up correctly now 🙂Have a nice day,
StefanoAttachments:
Still same error. Please double check (or associate the email webmaster [at] {thisdomain}.com to the account so I can reset the password myself 🙂 )
I am a bit at a loss here – would you mind creating me a temporary admin account so I can personally investigate and fix the issue? You can post the credentials here and mark the reply as private: I will be the only one allowed to see it 🙂
Have a nice day,
StefanoUntick the option “Hide posts that do not reach the threshold” and the issue should be fixed 🙂
Have a nice day,
StefanoHi Charles,
I am afraid there is currently no way to hide that tab. We may ship that as a feature in future releases, but it is not supported as of now :\Have a nice day,
StefanoHi there,
you cannot select it for payment because its Due payment value is zero. Check that you do not have a threshold set in Options > Counting settings > Total payment 🙂Let me know!
Have a nice day,
StefanoHey James,
glad to know the plugin is useful! 🙂So, we do not have an explicit API for replacing the Adsense module with a different revenue source. What we do provide, however, is a very simple abstraction for adding a new payment criteria (say you’d want to pay per links in a post, or per posts in a given category, or whatever). We have a simple method you can invoke that will have your own payment criteria installed seamlessly. This could easily add you a column in the stats table and integrate it with all the payment features, but you’d still have to draw fetch data from the new source and put them in the database. This we are currently doing with the class ppcp_google_analytics_class.php, where we have a bunch of routines that regularly pull data from Google Analytics and stores them locally in your database. I guess most of this could be recycled for your other platform, but can’t guarantee. I would guess it would require some effort though 🙂
Not sure this helps: do get back for anything more! 🙂
Have a nice day,
Stefano
