anmari

It looks like that code is complaining about either a start or end limit, either from a shortcode parameter or if there weren’t any, then defaulted from ‘now’, but ONLY when the limit is not already a date object.
On my test system with no parameters the defaulted ‘start’ is always a date object, so I am not getting that message.

Do you have a start= or end= in the shortcode parameters?
Is there a further message that says what the invalid date is?

If you dom’t have that many current events, consider maybe just setting up a new calendar. Or creating your events in wordpress ??

This may help https://icalevents.com/5142-memory-problems-or-timeouts/. Seeing that your messages on happening in the ‘rrule’, it may be the effort in processing recurring events thats too great. Read the link, try tweak your parameters and clean up your google calendar. You’ve been a long term user, possibly your google calendar has a lot of old stuff in that has to be checked.

For the benefit of others, it is looking like the site Erik is working with never had a purchased amr-users-plus addon.

Re the ‘upgrade’link that Erik mentions. It takes on to https://wpusersplugin.com/related-plugins/. A human still has to decide which additional functionality they want and after buying one of the add-ons, a human still has to manually install the addon plugin from the zip file oneself, the first time.

For most addons, once installed and a license key entered, then auto updates will work.

For the avoidance of any future confusion, perhaps I shall probably change the text ‘upgrade’ to something like ‘add functionality’?

What’s the problem? yes either use [do_widget id=bp_course_widget-5] with classic widgets or use the name, ensure it is the correct name.

It is in the css you are using (the 2017 one) either choose a different css, no default css or add css to not display whatever you don’t want to display.

It sounds like you have not yet discovered the joys of the browser tool ‘inspect element’ – it is very helpful to figure what css is applying to which element and from which stylesheet.

View post on imgur.com

Use css. https://www.google.com.au/search?q=how+to+center+a+div

How you actually do it depends on your theme and the css classes you are using, and the width of the element and what responsive / different screen sizes you want to allow for.

This is css support and beyond the scope of support of this plugin.

I assume you mean you want to ‘shortcode’ a text widget for re-use? Have you read https://www.ads-software.com/plugins/amr-shortcode-any-widget/#installation.

EG:
[do_widget id=widgetid title=false class=whatever]

Apologies – I had another look and see now that I jumped to an idea of what your raw data was based on looking at your csv in excel, not in csv. And excel had switched the format – classic mistake.

I should have waited for you to figure out how to look at your raw data.

I was correct however in that the addon currently only caters for ISO (International Standards Organisation) date time YYYY-MM-DD and unix timestamps.

The raw data does have year first which is why the text range works for it. The problem with using the jquery datepicker date string, is probably that in searching with the date picker for everything between say 2021-08-dd and 2021-09-dd, one is not going to find the records with 2021/08/dd.

I’ll have a look at how best to cater for this and see if I can add it in, convert the datepicker format to whatever people say their date format is (so long as years are first ?? )

Yes it is a useless way to store dates if one is expecting to do any logic or SQL querying comparison on then.
Good luck !

Ha! found it – I saw you had the CSV extract enabled, and that extracts raw data.

Whatever you are using to create those date fields, appears to have them stored as dd/mm/yyyy which is very unhelpful in multiple ways, not to mention dangerous. Those are basically ‘strings’, not date fields in the DB. I suggest you see if there is a way to create true date fields as expected by MySQL https://dev.mysql.com/doc/refman/8.0/en/datetime.html and by wordpress, like the user registration field. Then any sorting and querying by less than / greater than becomes easier.

The only reason the plugin appears to handle these is because there is php function tries a best guess based on commonly accepted formats https://www.php.net/manual/en/function.strtotime.php. Slashes are usually thought to be american with mm/dd/yyyy, however yours have 26/10/21 sp are not american.

Re phpmyadmin – this is either via your hosting control panel or there are some plugins where you can run it inside wordpress or from wordpress.
If you are maintaining your own website, it is a really good idea to have some understanding of the database and the data.

Use phpmyadmin and look at the wp user meta table for your fields.

It doesn’t matter how you format the fields. In fact, right now it is probably better if you don’t format those fields at all, just so we can see their ‘raw’ form if you don’t how to look at your database. Looking at formatted list doesn’t help.

The formatting routines are very forgiving, they will try make sense of any date format. The date range selection CANNOT be. For that the dates MUST either be in YYYY-MM-DD or unix timestamp format.

Update went up.
Use “Elin” (with the double quotes) to search where field only has Elin
Use elin -stuffyoudontwant to exclude records that have stuff you don’t want.

Hi, I cannot see your page, login required.
Please check how your field’s date is actually stored (not how you have set the field type, or how you have chosen to format it, but how the data is actually stored in the database).

I have just re tested on both yyyy-mm-dd dates and unix dates, and it is working for both.

See https://directories.wpusersplugin.com/alpha-nav-list/ for normal dates and
unix dates here https://directories.wpusersplugin.com/profile-grid-user-list/.

I did find some little bugs (field label on unix date range) and a possible failure of jquery-ui css to load because it had http not https, so I’ll be pushing an update 1.2 out for those. But otherwise the base functionality works.

So then the next step for you would be for you to investigate your data.