Scratching my head with a specific setup for member-only content (currently using Woo Memberships and Woo Subscriptions).
The project has a large number of downloadable products which are available for purchase as one-offs. So far so good :)
However, those downloads should be available for free for paid members - a bit more tricky.
Besides that, only those downloads that are published during the membership period should be available for free - every product has a custom field that contains month and year the product belongs to.
For example, if I'm an active member since Jan 2019 - I get free access to downloads for Jan 2019, Feb 2019 and so on.
If I used to be a member from Apr 2018 till Dec 2018 - I get free access to downloads for Apr 2018, May 2018 and so on.
Any tips how to build such setup? Should I consider EDD (or maybe something else) instead of Woo? I'm almost ready to begin modifying https://woocommerce.com/products/woocommerce-subscription-downloads/ for this, but thought maybe someone else has done anything similar before?
A little late to the party on this one, but I think that a plugin called S2Member might be really good for this case.
Related
library(Quandl)
library(xts)
Quandl.api_key("your_api_key")
cl <- Quandl("CME/CLU2022", type = "xts")
This data ends on June 30th 2022. As of today 7/14/2022, it should have data out to 7/13/2022. Thank you!
I experienced the same issue. I have seen no price updates past June 30, 2022.
Unfortunately, it looks like NASDAQ has acquired Quandl and they are in the process of deprecating the CME EOD price database/API.
From Nasdaq data support:
Kindly be advised that the free CME futures database has been
deprecated. Moving forward, the data will no longer be updated and may
no longer be accessed. We're very sorry for any inconvenience caused
by the deprecation of the free CME futures database and we don't have
an equivalent database available on Nasdaq Data Link at the moment.
Please note that free data feeds may get deprecated at any time for
various reasons eg. they may no longer meet our quality standards,
they get copyrighted, technical issues prevent us from obtaining the
data, etc.
Unfortunately, we do not have a similar database on Nasdaq Data Link
that may serve as an alternative.
I found this site which allow me to scrap the announcement title and date. However, the amount of announcement is limited to 20. See image below, anyone know where I can scrap the title and date for each announcement for the fiscal year 2021
https://www.asx.com.au/asx/1/company/CBA/announcements?count=50&market_sensitive=false
The API is limited to 20, it is an undocumented API, other than spending time working with the API to figure out other ways around it, they don't provide any other method of getting results outside the bounds of the 20 results.
If you want more, you're going to have to find another service, which likely involves paying or writing more code.
I have a script that creates Google Calendar events (via the Google Calendar API), inviting/auto-accepting the classroom, teacher and students (all users within our G Suite for Education account). (Yes, it is written in Perl but I don't think that is the problem.) Using this script, I manage 500-600 calendar events per school day.
There is enough rate limiting in the code and quota available in Google API Console that I can create a couple months worth of events in a nightly run. So I usually push one grading period into Google Calendar at a time. (I have over 37,000 events for this 2021-22 school year already pushed to Google Calendar.) This has worked since August 2018.
But, for the past month or so, if I try to create events after mid-January 2022, I get a "Forbidden (403)" after about 50 events are created. However, if I need to change 2021 or early 2022 events (for example, there is an assembly scheduled at school and the class times change, or a class moves from one room to another), I can delete/update/create the usual thousands of events per run with no problem.
As an example, tonight's run deleted and re-created 517 events for January 5, 2022 (there was a schedule change for that day) and made a few other miscellaneous changes, but only created 50 events for January 13, 2022 before a "Forbidden (403)" I'm not going to be able to create anything for a few hours. But, after that (or tomorrow), I'll be able to create 50 more events and then hit the same error again.
Did I miss a change to the API effective with events scheduled in the second week of 2022?
If you are confident that the quotas you use are way below the limits, you might be affected by a bug
There is a already an issue filed on Google's Issue Tracker where several users complain about limit being reach while console shows only 2% of limit being used - so similar to your case.
I recomend you to "star" this issue to increase visibility.
However, beforehand it might worth contacting the Google Workspace support. They can look into your quota usage and see if you are using some "idden quota" you ar enot aware of.
I am in need of a plugin or any codes, ideas that will make a specific wordpress user have a list of monthly report(payment transactions, account status).
I know it is confusing but what I mean is:
- every month or two, admin will update user savings/credits
- and the user can view his/her current savings/credits
- the user also can view the past report updates
Sample:
Current Savings: #800
Mar 05 - $700
Feb 02 - $400
Jan 02 - $100
When they click one of the past records, they will go to a page with a complete details of the transaction.
NOTE: All payment/transactions are made online. This is just for viewing purpose only. Users cannot edit anything except for their profile.
Can wordpress do this? or I should go with hardcode php? I prefer wordpress because it is convenient to use
Thanks Everyone
Sounds very much like a custom feature which will require you to build it unless you're payment gateway provides this type of functionality for you.
However, you say that the admin will update some values each month. If you're using custom fields, you can use the custom fields plugin to display the values.
I'm making a timeline in Wordpress, and I'm trying to make a post with the date January 12, 1800, but Wordpress doesn't allow me. Apparently, it doesn't let me post anything before the year 1970. Is there any way to fix it?
PHP (the programming language WordPress is written in) uses a unix timestamp, which is the number of seconds since the 1st January 1970. This means that you can't use dates before that date, as that's "the beginning of time" according to PHP.
Sorry if that wasn't the answer you wanted :(
I'm fairly sure this isn't a Wordpress problem, more specifically a PHP problem which has led to Wordpress dealing with it.
This excerpt is taken from the PHP Manual:
The valid range of a timestamp is typically from Fri, 13 Dec 1901 20:45:54 GMT to Tue, 19 Jan 2038 03:14:07 GMT. (These are the dates that correspond to the minimum and maximum values for a 32-bit signed integer). However, before PHP 5.1.0 this range was limited from 01-01-1970 to 19-01-2038 on some systems (e.g. Windows).
So it may not be a problem with Wordpress itself, you may need to get in touch with someone at Wordpress about the problem, perhaps they can implement PHPs calendar extension.
Here are two solutions I came up with:
http://studiohyperset.com/wordpress-old-dates-historical-pre-1969-pre-1970-timestamp-function/3102
If all your dates are going to be in the 1800s, perhaps you can configure Wordpress to show the date in 2 digit format and stick "18" before it.
Some people claim to be able to use pre-1970 dates, though the bug is still offically open for 3.0: WordPress › Support » Bug with backdated post before 1 January 1970 - wp2.8 It's alleged that the problem is the se of negative time stamps, which some server OS's can't handle.
Could a custom field be used for the year earlier than 1970 and while printing the "current" day and month?
You can put the date into a custom field and display that instead and you could sort by that custom field as well, so the end result wouldn't be any different.
You can use Custom Fields to store the date, and show that in place of the_date or the_time calls.