actronab

.tablepress .column-4 a:hover {
    background: green;
}

Hello,

okay, I see. What about an option to enable or disable the additional wrappers? This way you wouldn’t break downward compatibility for existing installations, but introduce more flexibility to style the table layout, if desired.

I mean, I could fork your plug-in at any time to introduce custom markup, but I’d like to stick to your stock implementation, so that I can benefit from further updates and security fixes.

Kind regards,
Bernd

Hello,

why not wrap elements before and after the table individually? I think it might cause further trouble, if the table is included in the wrapper as well (in terms of alignment and positioning).

Or are you afraid of breaking downward compatibility by introducing two wrappers?

Visually, they should not bother too much, if you chose an inline element (like <span>) with no styling, don’t you think so? Those who need it, could however use those wrappers for individual styling.

Kind regards,
Bernd

Nah, for semantic reasons I’d rather like to keep the table name and description separated. That’s why I came up with the idea to wrap elements before and after the table in a wrapper element, so that developers can style the components, if they like to do so.

Hello,

but turning both elements to display: block; will separate them and table name and description will no longer be in the same line. Or am I missing something? That’s why I altered the display attribute in the first place.

I want the table caption to look like this:

Earnings: Monthly income by region in 2020.

Where “Earnings” is the table name and “Monthly income by region in 2020.” is the table description. This works fine, I just cannot center the entire caption this way.

Kind regards,
Bernd

• This reply was modified 4 years, 1 month ago by actronab. Reason: Edited blockquote

All right, thank’s for your reply. Glad to hear that you are not logging any data to share for commercial purposes. Just wasn’t sure what “is supported by” was supposed to mean in this context.

No, unfortunately I can’t. I’m still testing the plug-in locally in my dev environment.

But I simply created a table, chose to print both table name and table description under the table and then added the CSS code, I already mentioned above, to style the caption.

It is all printed in one line now, as desired, but always aligned to the left. However, I’d like to center the line that contains the table’s name and description.

I’ve tried to work my way around with text-align: center; ans also tried to center with margin: 0 auto; but had no luck yet. In my opinion a wrapping parent element is missing to properly center the elements.

But if you know a workaround that does not require additional elements, go ahead, I’m listening! ??

Thanks!

What if I upload an 2100px image then and have a resolution of, let’s say, 3840×2160 px? Eh? And I [redacted] KNOW how to fix the CSS code.

> Akhlesh Nagar (@akhlesh-nagar)
> We will fix this issue in our next update.

This is ridiculous. Three different people of your team have been responding to this post now. The issue has been reported 1 month and 3 weeks ago. Why don’t you fix the base template? I don’t want to fix each and every bug that you cause in my child theme.

• This reply was modified 4 years, 1 month ago by Steven Stern (sterndata).

Yeah yeah yeah they’ve fckd that up…

https://www.ads-software.com/support/topic/latest-update-broke-entire-site/

Either add your child theme’s name at two locations in the companion plug-in (file webriti-companion.php) or rename your child theme to Appointment child. Expect more problems in future.

Hello,

Please take a look at my web site here:
https://appointment-green.webriti.com/

The slider images used to have a width of 100%, but in one of the last updates it was changed (see initial post).

See difference here:

Appointment theme slider

Kind regards,
Bernd

Layout is still broken with latest update. Why don’t you fix the parent theme?

Just stop messing with the code if you don’t know what you are doing.

The theme is getting worse with every new release.

Why don’t you fix general problem in parent theme? CSS styles are still faulty.

Yah, I’ve fixed that for myself already. But if you will address that issue in MetaSlider, I don’t have to clutter my child theme with that fix.

Thanks, disabling autoplay made debugging significantly easier.

I could now identify what changed with the last update. CSS code of Nivo 3.18.0 contains a new loading animation that did not exist before. It is defined like this:

.theme-default .nivoSlider {
  background: #fff url(loading.gif) no-repeat 50% 50%;
}

Setting the background color to #fff here causes the issue, because it creates those white margins on each side of the slider image.

It should be something like this

.theme-default .nivoSlider {
  background: transparent url(loading.gif) no-repeat 50% 50%;
}

or the background definition should be omitted altogether.

Is that something you would fix within MetaSlider or is this a Nivo issue that needs to be fixed in a different project you rely on? Should I fix this issue locally within my theme, because it is specific to my side or does it make sense, if you fix it in your plug-in?

• This reply was modified 4 years, 6 months ago by actronab.