Problems after update to 2.1.20

Resolved ffortissimo
(@ffortissimo)

3 years, 11 months ago

After updating the plugin to version 2.1.20 I found the following problems:

1. The following strings aren’t translated to Dutch while those are mentioned in the .po
“USERNAME OR E-MAIL”
“PASSWORD”
“KEEP ME SIGNED IN”
“Forgot your password?”

2. The sign-in button won’t be changed by my own css for buttons. This did work in the previous version. Do I need to create .um-button in my CSS from now on?

The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)

Thread Starter ffortissimo
(@ffortissimo)

3 years, 11 months ago

@1
The site language is set to Dutch.

@2 I created a new entry ‘#um-submit-btn.um-button’.
But it’s strange that a plugin wants its own css.

Thread Starter ffortissimo
(@ffortissimo)

3 years, 11 months ago

The same goes for the other pages.

missveronica
(@missveronicatv)

3 years, 11 months ago

@ffortissimo

#1. Use your translation plugin and do a Sync.

The Loco translate plugin documentation:
https://localise.biz/wordpress/plugin/manual/sync
Thread Starter ffortissimo
(@ffortissimo)

3 years, 11 months ago
Forgot to mention that one.
I already tried the sync options in Loco translate plugin.

But.. I found it.
In Loco Translate > Languages there are 3 languages:
- English (United States) en_US
- Dutch nl_NL
- Dutch (Formal) nl_NL_formal
There are 2 options for Dutch in WP.
The problem about the language has been solved 😀
Thank you for the wake up call @missveronicatv
- This reply was modified 3 years, 11 months ago by ffortissimo.
Thread Starter ffortissimo
(@ffortissimo)

3 years, 11 months ago
I’ve added the following in my custom stylesheet, but imho the plugin should follow the site colors.

Is there another solution, is this a bug or should it be a RFC?
```
/* ultimate member account */
.um .um-tip:hover,
.um .um-field-radio.active:not(.um-field-radio-state-disabled) i,
.um .um-field-checkbox.active:not(.um-field-radio-state-disabled) i,
.um .um-member-name a:hover,
.um .um-member-more a:hover,
.um .um-member-less a:hover,
.um .um-members-pagi a:hover,
.um .um-cover-add:hover,
.um .um-profile-subnav a.active,
.um .um-item-meta a,
.um-account-name a:hover,
.um-account-nav a.current,
.um-account-side li a.current span.um-account-icon,
.um-account-side li a.current:hover span.um-account-icon,
.um-dropdown li a:hover,
i.um-active-color,
span.um-active-color
{
    color: #eb5955;
}

.um .um-field-group-head,
.picker__box,
.picker__nav--prev:hover,
.picker__nav--next:hover,
.um .um-members-pagi span.current,
.um .um-members-pagi span.current:hover,
.um .um-profile-nav-item.active a,
.um .um-profile-nav-item.active a:hover,
.upload,
.um-modal-header,
.um-modal-btn,
.um-modal-btn.disabled,
.um-modal-btn.disabled:hover,
div.uimob800 .um-account-side li a.current,
div.uimob800 .um-account-side li a.current:hover
{
    background: #eb5955;
}

.um input[type=submit]:disabled:hover {
    background: #eb5955;
}

.um input[type=submit].um-button,
.um input[type=submit].um-button:focus,
.um a.um-button,
.um a.um-button.um-disabled:hover,
.um a.um-button.um-disabled:focus,
.um a.um-button.um-disabled:active {
    background: #eb5955;
}

.um a.um-link {
    color: #eb5955;
}

.um-profile.um .um-profile-headericon a:hover,
.um-profile.um .um-profile-edit-a.active {
    color: #eb5955;
}

/* input-knop ultimate member */
#um-submit-btn.um-button {
	background-color : #eb5955;
	border-radius : 0px;
}
```
- This reply was modified 3 years, 11 months ago by ffortissimo.
Plugin Contributor Champ Camba
(@champsupertramp)

3 years, 11 months ago

Hi @ffortissimo

Custom CSS settings have been removed since version 2.0. You can check the CSS selectors here for your reference: https://docs.ultimatemember.com/article/270-how-to-change-default-ultimate-member-blue-color-using-css

Regards

Thread Starter ffortissimo
(@ffortissimo)

3 years, 11 months ago

I did search the faq and didn’t see it, my apologies.

Thank you very much.

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Problems after update to 2.1.20’ is closed to new replies.

Tags