morespinach

Even with the dates being stored in some weird way such that June 2014 is considered older than March 2012, the issue is that the events are NOT showing up on the site at all.

I have five events in june.

This is the events calendar on the site:
https://thearcofluzernecounty.org/events-calendar/

What gives?

I enabled the debug option, but the “Debug Bar” plugin does NOT work in WP 3.9.1. And all that this events plugin is writing to the PHP log is the following useless line:

[Fri Jun 13 23:29:58 2014] [error] [client 75.126.12.52] The Events Calendar Log: Initializing Tribe Events on Jun, 14th at 03:06:58 am
[Fri Jun 13 23:30:05 2014] [error] [client 75.126.12.52] The Events Calendar Log: Initializing Tribe Events on Jun, 14th at 03:06:05 am, referer: https://thearcofluzernecounty.org/events-calendar/2014-03/
[Fri Jun 13 23:30:08 2014] [error] [client 75.126.12.52] The Events Calendar Log: Initializing Tribe Events on Jun, 14th at 03:06:08 am, referer: https://thearcofluzernecounty.org/events-calendar/2014-02/
[Fri Jun 13 23:30:10 2014] [error] [client 75.126.12.52] The Events Calendar Log: Initializing Tribe Events on Jun, 14th at 03:06:10 am
[Fri Jun 13 23:30:23 2014] [error] [client 75.126.12.52] The Events Calendar Log: Initializing Tribe Events on Jun, 14th at 03:06:23 am, referer: https://thearcofluzernecounty.org/site/wp-admin/post.php?post=443&action=edit

I just deleted the old plugin, and installed the new one. Fortunately old events show.

But when I create a new event, it does NOT get saved. Even when I publish it. What gives? Where are the events going?

EDIT:
Upon some investigation, it seems the dates of the new events are getting stored in some format that makes them show up at the bottom of the Events Listing in the admin area. Why’s this? Why is “June 14, 2014” older than “March 20, 2012”?

In what way is the new plugin saving these events?

Something is wrong, because when we click on the event’s preview link, or its permalink, we get a 404. Other threads related to 404 here seem to be unanswered too. What gives?

This is a fresh install of the plugin!

We use MySQL Ver 14.14 Distrib 5.6.16, for Linux (x86_64) using EditLine wrapper.

Oh ok. I guess my browser is just caching the first page load then? Thanks so much. This is now my favorite caching plugin. So simple and functional. Better than hyper cache etc. Thanks!!

Thanks. Very useful! Hope it also helps someone.

Thank you. Could you let me (and others here) know what fix was needed?

Thanks

It neither works on my localhost, nor on the website. It has never worked, ever, with HTML. Hence the question. What am I missing?

Screenshots as proof…

Inside the WP admin area:
https://i.imgur.com/Q9d1Hcy.png

How it shows up on the website:

View post on imgur.com

Nope, that doesn’t work. It simply prints out the html…as if it were a <pre> tag in HTML. How can I make it print the HTML as real HTML, not as code?

Is it possible to include HTML in the messages?

I’m getting the same issue. What’s up with this plugin?

Pages, tags, categories work fine. Only the posts, which are the most important, are completely empty.

OK, it works now. It was MY mistake — I had some old “UPLOAD_URL” etc settings in my wp-config.php, which I have now deleted. Now it works!

That’s what it is now, and it doesn’t work. (This is what I explained in my original post)

In the media section, when I click on ‘edit’ on a file, the path is still the long path with ‘wp-content/cdn’. Hence my confusion as to what this plugin actually does.

Thanks. But second is not what I want. The cdn.domain.com is already mapped to wp-content/cdn. The usual ‘origin pull’. Any ideas? Or is that not what this plugin does? (In which case I don’t know what it does — because getting the long URL already works with default wp!)

Thanks

For anyone having the same issue, if it helps, this is what I did: I created a regular timestamp field in the table for this plugin.

Important to have the default value as “CURRENT_TIMESTAMP“. This way we don’t need to muck around with the INSERT and UPDATE queries.

Only in the view function, make sure the “GROUP BY” is by this new field, and not by the usual “submit_time“.

How I wish the developer was not trying to be over-creative with that decimal rubbish. There’s a reason the TIMESTAMP type exists in the DB. Not many people need to store microseconds.

Just to add. The idea to store the submit_time field as decimal(16,4) is not a smart one at all. Why not just rely on a timestamp, which already exists? That way the queries will work. Right now the decimals of time are basically the same across most records.

The submit_time should be timestamp, and should default to now() or something. It’ll be much cleaner that way, and more importantly, it would at least work!

I looked into the PhyMyAdmin for this plugin. In the database, the query is being grouped by “submit time”.

This is a horrible piece of code!

The “submit time” is mostly the same for many concurrent submissions. As such the grouping (which therefore needs that each field is shown based on MAX(if.. statements) is flawed too.

Any thoughts on how I can better query the data to show each unique submission?