lauritasita

Hi Brecht,

If I want to use CSS to edit that property could you tell me the how that would look? It doesn’t seem to work if I code it this way because I need to be able to the post title property and this will only edit the summary information under it: How do I code the CSS to edit the post title only?

.vlp-link-container, .vlp-template-default {
background-color: #000000 !important;
color: #00ccff; font-size: 14px !important;
line-height: 1em !important;
}

Thanks.

Thank you, Brecht,

Is there a way to adjust the line height of the post title? Some of the post titles I have a very long so they wrap around to the next line with a double space. Can that be adjusted in the CSS? It would be applied to all the posts titles.

• This reply was modified 1 year, 6 months ago by lauritasita.

Hi Brecht,

I just want to know if it is possible to have a different color for each post on the page. Right now, I figured out how to change the color from white to blue for all of them using CSS, but is there a way to have a different color for each post?

Here is how my CSS currently looks to change the color to blue on my website which has been working:

.vlp-link-container, .vlp-template-default {
background-color: #000000 !important;
color: #00ccff; font-size: 14px !important;
}

Are there settings in the plugin to do this for each individual post?

Here is the link of how your plugin currently looks on my website with my CSS:
https://clientswebdesigns.com/sanssouciblogs/

It’s on the homepage of the website, but you need to scroll down to the heading that says, “Featured Series Mini Books”. It’s under that heading.

Also, on a mobile device, is there a way to add some padding between the post image and the post title? They look too close together on the iPhone.

Thank so much.

Do you know when the next release will be out with the fix? Should I keep checking the plugin page? I just want to make sure I don’t update the site with the old version with the error in it.

Hey Guys,

I uploaded the beta version with the fix to the two websites where I was encountering the error message. It ran successfully! I need to ask this question: In my WordPress plugin section, I’m getting a message to update to the the last version of MetaSlider 3.29.1 which was the last version which contained the error. Should I now ignore this version update since the beta version you gave me is running ok? Also, the error I was getting was not occurring on every test site installation, but should I still upload the beta version anyway? All my WordPress installations are running on PHP 8 which I just recently updated to. I read PHP 8 is not very backward compatible. This error is the first issue I’ve ever had with your plugin, but it seems ok now.

Thanks so much for all your help!

• This reply was modified 1 year, 7 months ago by lauritasita.

Hi Steve,

MetaSlider is a great plugin!

Yes, I can confirm that I’m using version 3.29.1 of MetaSlider on my website.

I have this issue occurring on my websites so this ticket should remain open.

Is anyone else having this issue?

Update –

I just clicked on the little toolbar on the upper right and when I recalled the plugin’s main page, I was able to see the other slideshows and I suddenly had the ability to change their names.

I don’t know if there’s still a bug, but it seems to have resolved on its own for now.

I still a nice easy plugin. Thank you!

Hi Jeff,

I activated the Tinymce plugin on a test site with your plugin activated and I was able to add features to the classic toolbar. Then I tested it out on a post and everything seems to be ok.

So far, I would say your plugin is compatible with the Tinymce Advanced plugin, but I will keep you posted if anything comes up.

When I mentioned www.remarpro.com, I was referring to the audio gallery playlist that you can create that comes with your WordPress installation which does not require a plugin.

My question is: can you enable autoplay on a playlist using this function.

The playlist shortcode does not seem to supply such a feature.

@adrianamandine –

I’m having the same issue. Everything was fine this morning, but when I made some changes to the posts, I got the same error.

The funny thing is that it actually did do the update when I clicked the “view post” link after I got the error message.

I reported this to my theme developer, but I had a feeling it’s a WordPress thing.

@dragonsjaw –

Thank you for telling me about it that plugin. It’s good to have more than one option, especially if the Classic Editor plugin gets phased out.

I actually discovered that plugin yesterday and installed it on one of my testing sites. So far, it works pretty well, but I really have to test it further.

@jakept –

I understand what you are saying here, but I still think that it was still not the right thing to do by ignoring the long time users, some of them that use their websites to run a business.

From what I remember from reading all the “Rave Reviews” on the Gutenberg Plugin forum, I was under the impression that the Classic Editor plugin was presented to the public as a permanent solution if people wanted to opt out of the block editor and they have every right to if they are uncomfortable using the block editor.

I have also started looking into other plugins out there that will do the same thing if the Classic Editor plugin is discontinued or phased out and I’m sure there will developers that will be more than happy to maintain it on a permanent basis or come up with other solutions.

@jakept –

At the present time, there certainly does seem like there is a demand for it, but I guess that can always change.

I upgraded a very large website this morning with no issues, however, I don’t see how I can possibly modify all those posts going back many, many years. I can only hope that by 2022 that the block editor has matured to a point where I may want to use it to save my website, but at the present time, it would not even be compatible with my plugins.

I think this is totally unethical. I feel the WordPress devs could have done this more smoothly. They are causing such a disruption. I do not feel like i’m part of the WordPress community anymore. This anxiety have been avoided.

I have read that the Classic Editor Plugin will only be supported until December 31, 2021, but hopefully after that, it will continue to be supported beyond that if the need is great for developers who still need it and their businesses depend on it.

Maybe @karmatosed could weigh in on this since it is very important to many users who want to continue to use it.