david4ww

Thanks for that Guido…excellent service.
I’ll update and work through it over the next few days.
David

Thanks for the response.

I don’t have any CSS attached to the vsel-container class. As you can see in my examples I was simply using the class attribute to add an additional class (or sometimes classes – for example like class=”vsel-container vsel-diary vsel-linear") and those are all defined within my custom stylesheet within the theme I use.

I’m not sure I entirely understand what the new class attribute will exactly do…but all I need is to be able to do is add bespoke class(es) to the events list as in my examples in my earlier post. If its as simple as using the attribute something like class="vsel-linear" that gets incorporated into the HTML to become class=”vsel-shortcode vsel-shortcode-upcoming-events vsel-diary vsel-linear" that would be fine. Is my understanding correct?

Hi Guido
Thanks for you quick response.

Your suggestion would be very helpful. I’ve been experimenting with various workarounds on this on a copy the website running in WordPress on my PC but I can find no easy (or quick) solution. I would like to stay using VSEL if at all possible because it exactly meets my needs (e.g. I do not need an all-singing-all-dancing events calendar plugin).

I believe I can live with what you suggest. Just to clarify with an example:

Currently to show a list of events (with category “social”) with additional formatting using my class “vsel-linear”, I do the following:

[vsel event_cat=”social” posts_per_page=”5″ date_format=”jS F” no_events_text=”No events announced” class=”vsel-container vsel-linear”]

This leaves the vsel-container class extant and applies some additional formatting. I have a collection of many such classes for controlling aspects of how events are displayed. I use these in shortcodes and also the widget.

I assume with your suggested next update I would instead do:

[vsel event_cat=”social” posts_per_page=”5″ date_format=”jS F” no_events_text=”No events announced” class=”vsel-shortcode vsel-shortcode-upcoming-events vsel-linear”]

as the “vsel-shortcode vsel-shortcode-upcoming-events” seems to have replaced the “vsel-container” in the HTML.

It works using Chrome but not using Firefox. Here are the console outputs for both.

Chrome :

JQMIGRATE: Migrate is installed, version 3.3.2
term.php?taxonomy=post_tag&tag_ID=178&post_type=page&wp_http_referer=%2Fwp-admin%2Fedit-tags.php%3Ftaxonomy%3Dpost_tag%26post_type%3Dpage:1 [DOM] Found 2 elements with non-unique id #description: (More info: https://goo.gl/9p2vKq) <textarea class=?”wp-editor-area” rows=?”20″ autocomplete=?”off” cols=?”40″ name=?”description” id=?”description” style=?”visibility:? hidden;?”>?</textarea>? <textarea name=?”description” id=?”description” rows=?”5″ cols=?”50″ class=?”large-text”>?…?</textarea>?

Firefox:

This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. term.php
JQMIGRATE: Migrate is installed, version 3.3.2 jquery-migrate.min.js:2:709
Some cookies are misusing the recommended “SameSite“ attribute 4
Cookie “SEARCH_SAMESITE” has been rejected because it is in a cross-site context and its “SameSite” is “Lax” or “Strict”. cse.js
Cookie “SIDCC” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite cse.js
Cookie “SEARCH_SAMESITE” has been rejected because it is in a cross-site context and its “SameSite” is “Lax” or “Strict”. cse.js
Cookie “SIDCC” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite cse.js
MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead. tinymce.min.js:2:8856

Apologies for resurrecting my query but I am now very close to putting my new site online and I want to get this right. I’ve watched the various videos many times but am still unclear about one specific point. It may not be an issue at all but just incase …

As I said in my initial post, the WordPress site on my PC (created using Bitnami stack) uses URLs of the form: https://localhost/wordpress/about/ – the /wordpress bit refers to the folder in the Bitnami stack where the site resides and the /about/ bit is a typical page.

Now on my live site I want that page to be https://www.mydomain.com/about/ NOT https://www.mydomain.com/wordpress/about/ – i.e. no /wordpress in the site URLs.

When I migrate, will duplicator automatically set up the URLs like that or will I have to do something in Step 3 of 4 to ensure that is what will happen (e.g. change any the fields in the New Settings section or the Options>Scan Options section so that the /wordpress bit is not used in the website URLs) and if so what settings would I need to change and to what.

Thanks

Worked out how do this … but it is not intuitive!
Rather than delete the category name, so leaving the field blank, I had to leave a single comma in the field. This then cleared the exclusion. IMO needs a (probably minor) fix.

Thanks Guido – very helpful.
I’ll wait for before diving in and hacking code to see if you have the time to come up with anything more elegant!
David

Thanks Guido.
I would rather not go down the route of changing the plugin itself if it can be avoided for the reason that you state and would obviously prefer some sort of shortcode attribute but accept that I may have to live without that option.

So, out of curiosity, I did have a look at the plugin files, and it would appear that perhaps all I would need to do is modify the vsel-page-template.php file at line 50 where a single date is output (I only ever use single dates) so rather than use esc_attr($date_format) in the sprintf() statement instead use esc_attr(‘jS F Y’) so that on event posts themselves the date always displays the year, then set the VSEL general date setting to just js F so the date without a year is used elsewhere (i.e. in my event lists)?

I have sent a screenshot to your support email address from your website. Hope that helps.

I think I may have the answer – it appears to be because I saved the WordPress login details for my domain in the browser meaning that I do not have to enter the password each time I login to work on the site. This results in the password fields in both the ACP settings page and the ACP user ‘login’ page when browsing to a ‘protected’ category being autofilled with my WordPress password. So whenever I clicked ‘Save Changes’ in the settings it saved my WordPress login password thus overwriting the ‘user’ password that I had set. If I do not save my WordPress login password in the browser it all appears to work as expected.