rkyburz

Hi @deevoice — see @hatesspam’s response above. I am facing looking for alternatives, too, and I have now installed the “Events Calendar” plugin—but I haven’t started transferring my events to the new plugin yet, as I have >400 event entries that would need to be dealt with, and right now, I would only tackle that if Events List were to break down completely…

My response above may seem unrelated, as I don’t use the “Heroic Table of Contents” plugin —?however: the issues appear to be related. In my case, the issues is not with the Yoast SEO plug (i.e., their TOC block), but with WP, or rather with a recent change to the Gutenberg plugin, which automatically adds anchors to all header blocks. In your case, you may have inherited this through a Gutenberg plugin update, while in my case I ran into this through the WP 5.9 update which again has incorporated recent changes to Gutenberg.
Automatic addition of HTML anchors to header blocks may be a good idea —?but it definitely needs an option to opt out for individual blocks. My workaround is to switch from header block to a plain paragraph, and to style that like a header. That’s not a universal solution, of course: for one, it’s clumsy, and then, converting headers to paragraphs may destroy your readability score (e.g., with Yoast SEO).
And a personal advice: don’t “abuse” header blocks for bold text / highlighting —?rather style a plain paragraph to make it look the way you want. In WP 5.8.3, you could probably deactivate the Gutenberg plugin to avoid the issue, but in WP 5.9, this would not help.

I see this with WP 5.9 / Yoast 18.0, where anchors are added automatically to all header blocks. The anchor text can be modified / shortened, but with this setting, eliminating a header anchor instantly re-fills it with the default text. This particularly hurts with the “Yoast Table of Contents” block. Up to WP 5.8.3 / Yoast pre-18, one could simply eliminate the anchor text in the sidebar widget. I’m trying to get this fixed through Yoast.

I’m running WP 5.8.3 / PHP 7.4.26 / Event List 0.8.6 —?and I can at least say that see no fundamental incompatibility. However, I wonder whether some of the known bugs / flaws are caused by this syntax error? Sadly, EL 0.8.6 feels like a partially orphaned plugin (even though I don’t know of any suitable alternative), and this is one reason why I feel shaky about moving to PHP 8.x …

Hi @fresatomica, thanks for your response.
Too bad! Interestingly, tiled mosaic galleries appear to display OK in AMP view —?however, tiled mosaic galleries have no controls, and so often end up taking up a lot of space. With this, switching to tiled mosaic in places where I want to have, say, 5 – 7 images in a horizontal strip is not an option, Plus, circles and square tiles are not an option because a) my images are never square, and b) because of my carefully crafted image proportions / esthetics, square and circular crops will almost inevitably destroy either the esthetics, if not the essential content. An option in which the AMP view would force tiled column galleries into, say, tiled mosaic (which appears to work for me) might be acceptable, at least as a temporary solution.
Addendum: some user controls in tiled mosaic galleries would be really useful!

sorry, I amended my last response after yours … here’s the latest addition again:

The post currently in the works reports “There are 40 issues from AMP validation which need review. The issues are not directly due to content here. The invalid markup has been automatically removed”. As these warnings are not directly related to the content of my post, I don’t see why I need to see a new instance of that same warning with every intermediate save! ??

Hi @albertomedina, I have “upgraded” my review to ***, reflecting the current state of usability (and the support that you are offering). I may further upgrade when I’m able to get (most of) these issues resolved. Will revisit the issue tonight / tomorrow, as time permits. I still feel flooded with those warning messages. The post currently in the works reports “There are 40 issues from AMP validation which need review. The issues are not directly due to content here. The invalid markup has been automatically removed”. As these warnings are not directly related to the content of my post, I don’t see why I need to see a new instance of that same warning with every intermediate save! ??

• This reply was modified 4 years, 2 months ago by rkyburz.
• This reply was modified 4 years, 2 months ago by rkyburz.
• This reply was modified 4 years, 2 months ago by rkyburz.

Yes, I noted that latter point, but remain confused about the Reader mode…

Hi James, thanks again for getting back to me so quickly. I’ll have a detailed look at this tonight. For now, let me just inject one small(ish) thing, as you mentioned AMP plugin modes: I find the GUI for switching between modes (Settings screen) highly confusing: the top seems clear — “Template mode”, followed by a button and an icon —?but further down it is anything but clear which button / icon is which mode —?especially as I don’t see a button to select the Reader mode. Some horizontal rulers / extra spacing / a different arrangement might help. am I missing something here?

thanks for getting back to me on this. I have spent some two full days switching between all three modes (some were much worse than others), I even checked with the author of the Gutenberg “Stackable” plugin (which seems to cause some of the <script> errors) —?needless to say that he was unable to fix this instantly. I tried all plugin options, checked my header hooks (I’m using the Exhibit / GeneratePress theme). I think I encountered the advice about turning off AMP developer tools, but was unable to locate this in my menus —?at some point I felt that this was simply taking too much of my time … I have temporarily switched back to your plugin and found all error logs still to be there (shouldn’t these be deleted when I delete the plugin?), I’m sending you the site health information separately. I understand that the JS policy in AMP is not new —?but the way and the persistence & abundance with which I (as user / site admin) was confronted with these error messages is not exactly nice, to say the least.

Hi Anna,
I don’t think I have the magic bullet for this one. I’m sure there is a way to do this in a global fashion, i.e., to have the plugin insert extra spacing between subsequent events?— however, support in this forum is scarce, and everybody seems to be waiting for the developer to resume work on this. Given that the plugin urgently needs an overhaul (I wish it was compatible with and using the block editor!), I personally don’t rely upon somebody to invest work in extra custom solutions on an outdated code base. However, I’m heavily relying on this plugin to work, so I’m desperately hoping that it will not suddenly be incompatible or—worse—break other things in WP. As a result, I’m doing all layout that can’t be controlled with the standard plugin by adding the required extra layout features to the individual event entries —?if necessary, by using the code editor. I have run into the issue with visual clutter / insufficient separation between subsequent events myself —?and here’s what I have done. First, my own events list (quite different from yours, though dealing with concerts as well):
Then, in order to avoid having to re-edit every single one of my >300 event entries over and over again, I am now relying on style sheets, via the “Simple Custom CSS” plugin. A typical event entry will end with something like

<hr class="event-separator" />

(...)

<a class="event-bloglinkstyle" href="some_URL" target="_blank" rel="noopener noreferrer">→ Blog Review (★★★★)</a>

<hr class="event-endline" />

whereby the classes “event-separator”, “event-bloglink”, and “event-endline” are defined in my Custom CSS as follows:

.event-separator {
	padding-bottom: 0px;
        width: 20%;
        margin-top: 0px;
	margin-right: 80%;
	margin-bottom: 20px;
	border-width: 1.5px;
}

.event-bloglinkstyle {
        font-size: 16px;
	background-color: #ffcc66;
	font-style: italic;
	font-weight: 500;
}

.event-endline {
	padding-bottom: 0px;
	height: 2px;
	color: #999999;
	background-color: #999999;
        width: 100%;
        margin-top: 24px;
	margin-bottom: 20px;
	border-width: 2px;
	clear: both;
}

I also rely upon Custom CSS for controlling the styles in the rest of the event-list output (including the sidebar widget). Sorry for lots of this looking clumsy —?it’s not the most elegant coding: I have over 25 years of HTML experience, but still am not an expert in CSS coding —?lots of this is the result of trial-and-error. Nevertheless the top code segment above to all my >300 event entries, I can now change the style of the extra separation ruler (spacing, color, thickness), as well as most other styling simply by changing that style in one file: my Custom CSS. I don’t say the ruler is ideal, but if you were to make its color transparent, e.g., with

	color: #99999900;
	background-color: #99999900;

(note the extra two digits for the opacity / transparency), then it will look like space. Note that the “clear: both;” property will probably not force the space beginning after the date box in the case of short event entries.
You have a nice WP Website (even though that recurring CD pop-up is slightly irritating)!
Best wishes, -Rolf

• This reply was modified 3 years ago by Jan Dembowski.
• This reply was modified 3 years ago by Jan Dembowski.

For me, the key in Tablepress importing was not so much about UTF-8 (which must be the correct option), but about using HTML masking / superstructure. No idea whether the events list (which I also use, but without importing) supports HTML imports (actually, I doubt it).

For another plugin (Tablepress) I export from a database application (FileMaker) into HTML format with UTF-8 coding, and that can be imported to Tablepress tables without any problems. Maybe this helps here, too?

Same here: I have updated to WP5, no change with the events list, neither the short code, nor with the widget (my event-list shortcode has lots of arguments, though). I assume this is about the GUI—in which case an update to WP5 should have no effect at all, I believe. If at all, there might be an issue with (re-)posting a page with the [event-list] shortcode in it (I have in the past seen adverse effects of specific plugins with (very specific) shortcodes in blog posts. But even that (in my case) did not affect the functionality of such shortcode, it’s rather the other way around, i.e., certain shortcodes (e.g., [gallery … ) causing problems with specific other plugin functionality.
Did you perhaps insert event-list CSS code into a CSS file that got wiped out during the upgrade? In this case, I strongly recommend using “Simple Custom CSS” or a similar plugin to collect your customization code in a safe place.

Hi danniee, sorry for this being non-ideal. I use the “simply exclude” plugin exclusively to exclude specific *pages* from the search — and for this it seems ideal. I do concede, though, that the mechanism to exclude a category such as events, looks convoluted (from a quick look at the GUI—I haven’t tried that, really). Some of this may caused by the fact that (if I remember this correctly) events just migrated from pure database content to a special post type, and from messages in this forum I also seem to remember that this migration isn’t complete yet. I suspect that if events really were regular “posts”, then excluding them using using “simply exclude” would be almost trivial.