WP SMS messes up WooCommerce fields and other themes and plugins (RTL & LTR)

Hi @mansourikhah,

Thank you for opening this thread and sharing the images with us. We truly appreciate your efforts in helping us understand the issue.

However, we’ve not been able to replicate the problem on our end. To assist further, could you please try the following steps?

1. Deactivate all plugins except for WP SMS and WooCommerce and check if the issue persists.
2. Test with other themes to determine if the issue might be theme-related.
3. Re-activate your plugins one by one to identify if there are any compatibility issues with WP SMS.

We look forward to your response.

Best regards,
Matthew

Hi @mhdizmni,

I’m surprised you couldn’t reproduce it, I’ve been facing this problem for a long time on several sites.
And I had to use a css code snippet to solve this problem, part of which I’m posting here.

As far as I know, the problem stems from !important rules in the wp sms plugin.

.wpsms-wrap .select2-container--default .select2-selection--single, .select2-container--default .select2-selection--multiple, .select2-container--default .select2-selection--single, .select2-container--default .select2-selection--multiple {
	min-height: unset !important;
}

.select2-container--default .select2-selection--single .select2-selection__arrow {
	top: 1px !important;
	right: auto !important;
	left: 1px;
}

.wpsms-wrap .select2-container .select2-selection--multiple .select2-selection__rendered, .select2-container .select2-selection--multiple .select2-selection__rendered {
	display: unset !important;
}

As you said, I tested again on a new environment with only the wp sms plugin, WooCommerce, and the default WordPress theme enabled, and the result was the same.

Dear @mansourikhah,

Could you please let us know which versions of WP SMS, WooCommerce, and WordPress you are currently using?

Thank you for your assistance!

Regards,
Matthew

Yes, definitely, they are the latest versions.

WordPress Current version: 6.7.1
WooCommerce Version 9.5.1
WordPress SMS Version 6.9.9
Twenty Twenty-Five Version 1.0

Thank you, @mansourikhah!

I have escalated this matter to our team for further review and investigation.

We will keep you updated on any progress.

Thank you for your patience!

Regards,
Matthew

Great,
I will share the CSS snippet I am using to solve this problem on various sites and I hope this problem will be solved soon.
It should be noted that I am running this CSS code through the Code Snippet plugin and only in the admin area.
And I also saw other problems in the admin area on various pages that I did not add to this list and ignored.

.select2-container:not(.TB_ajaxContent) {
    /* min-width: 285px; */
	min-width: unset;
}

.select2-container {
    /* min-width: 350px; */
	min-width: unset;
}

.wpsms-wrap .select2-container--default .select2-selection--single, .select2-container--default .select2-selection--multiple, .select2-container--default .select2-selection--single, .select2-container--default .select2-selection--multiple {
    /* min-height: 46px !important; */
	min-height: unset !important;
}

.select2-container--default .select2-selection--single .select2-selection__arrow {
    /* top: 8px !important; */
    /* right: 7px !important; */
    top: 1px !important;
    right: 1px !important;
}

.wpsms-wrap .select2-container .select2-selection--multiple .select2-selection__rendered, .select2-container .select2-selection--multiple .select2-selection__rendered {
    /* display: inline !important; */
	display: inline-block !important;
}

.select2-container--default .select2-selection--multiple {
    /* padding-bottom: 5px; */
    /* padding-right: 5px; */
    /* position: relative; */
	padding-bottom: unset;
    padding-right: unset;
    position: unset;
}

.select2-container--default .select2-selection--multiple {
    /* padding: 3px 2px; */
	padding: unset;
}

.notice button, .notice input[type="submit"], .notice .button {
    /* padding: 10px; */
    /* margin-left: 4px; */
	margin-left: unset;
    margin: 0;
    padding: 0 10px;
}

Dear @mansourikhah,

I’m pleased to inform you that we have addressed the issue. The fix will be included in the next update.

Thank you for your continued support!

Regards,
Matthew

Dear @mhdizmni,

I’m glad to hear that. Thank you for your support.

Dear @mhdizmni,

It is unacceptable that the problem persists in the new version and this topic is unresolved. Why did you mark it as resolved?

Dear @mansourikhah,

The issue was addressed in this pull request, and we conducted thorough tests before the release to ensure everything was functioning as expected.

However, it seems the issue has not been fully resolved.

We sincerely apologize for any inconvenience this may have caused.

I’ve informed our team about the situation and marked this topic as unresolved. We will get back to you with an update as soon as we have more information.

Thank you for your understanding.

Regards,
Matthew

Dear @mansourikhah,

We have addressed the issue and it will be included in the next release.

In the meantime, you can download the development version of the plugin from our GitHub at https://github.com/wp-sms/wp-sms/tree/development.

If you’d prefer, you can also download the plugin using the link below:
https://www.dropbox.com/scl/fi/jlb3sn1os9rupwu0hyaui/wp-sms.zip?rlkey=w1dzwuldh07sls7e53gowqe9m&st=74gnxljz&dl=0

Thank you for your continued support!

Regards,
Matthew

Dear @mhdizmni,

Thank you for following up on this issue.

Dear @mhdizmni,

Do you consider this problem solved?
I came to check after more than a month and saw that there was absolutely no change in the situation I described.

Dear @mansourikhah,

We would like to inform you that a new release, which includes the fix for this issue, will be available in the next few days.

In the meantime, you may use the development version of WP SMS before the official release, as mentioned in this comment.

Regards,
Matthew

Dear @mhdizmni,

I understand, since you had a release from that time, I assumed that the changes were applied to that version.

Thank you