where to change the color of upload file name

Hi @mubiesam,

Trust you are doing good today, and thank you for reaching out to us.

I am afraid this is not possible out of the box. Can you please try the following CSS?

.forminator-ui#forminator-module-362.forminator-design--default .forminator-file-upload > span {
    color: #fff;
}

I hope that helps.

Kind Regards,
Nebu John

Hi Nebu @wpmudevsupport14

Thanks for your quick response, but it has nothing changed after putting your CSS in the Custom CSS under Appearance.

Any idea what might be wrong?
Thanks

Hi @mubiesam

I hope you’re well today!

Are you using any kind of cache on site and/or server?

If yes, would you please purge it fully? Cache is often an issue with such CSS changes so it’s important to flush it after changes are made. Also, once that’s done, please check the form in browser incognito mode (as some CSS may also be cached in browser).

Let us know if this makes any change, please.

Kind regards,
Adam

Hi Adam @wpmudev-support8

Thanks for your reply.

I had purged cache in Cloudflare, refreshed VM instance in GCP, and cleared cache of Chrome, but still nothing changed.

https://dahodan.johocen.com/share2video/

Checked the form in browser incognito mode, same result.

screenshot of CSS added

Any suggestion…
Thanks

Hi @mubiesam

Thank you for response!

I double-checked it and you are right, this CSS doesn’t work as expected. It actually works when added directly in browser but if added via form’s “Custom CSS” option it has to be slightly different.

Please replace it with this one:

.forminator-file-upload > span {
    color: #fff!important;
}

Then again update the form and clear all cache on site/server (note: there’s no need to refresh VM instances; just clear caches) and it should be fine. I just tested it on my own setup to make sure.

Best regards
Adam

Hi Adam @wpmudev-support8

Still doesn’t work, nothing changed with new CSS

Any other suggestion…
Thanks

Hi @mubiesam

I’ve visited the page that you shared earlier and while I can see that text still isn’t white I also see that there’s this rule applied to it:

.forminator-ui#forminator-module-362.forminator-design--default .forminator-file-upload > span {
    color: #777771;
}

This sets that gray(ish) color and it seems like it is a custom rule. But it’s also cached by the CloudFlare, specifically this file is served from CloudFlare cache which would explain why I cannot see the code that I shared recently anywhere on site

https://dahodan.johocen.com/wp-content/uploads/sites/50/forminator/css/style-362.css?ver=1660747697

I’m honestly not sure what else can I suggest other than these two things:

1. do review all the custom code that you already added for this form to make sure that there’s no “conflicting” rules (like the one shared above)
2. and double-check caching again; this particular file seems to be cached by CloudFlare so it’s possible that this is where it gets “stuck”

Kind regards,
Adam

Hi Adam @wpmudev-support8

Thank you for explaining the details, and I can see what you said in Chrome Developer Tools for the color remaining in #777771.

But it’s really strange that I had Custom Purged single file https://dahodan.johocen.com/share2video/ as well as “Purge Everything” on CloudFlare, and switched to “Development Mode” which will “Temporarily bypass our cache. See changes to your origin server in realtime.”

Unfortunately, still same problem.

Screenshots for above mentioned actions:
https://dahodan.johocen.com/wp-content/uploads/sites/50/2022/08/chrome_Db8qUHtBVP.png
https://dahodan.johocen.com/wp-content/uploads/sites/50/2022/08/chrome_n3jcA3DuT7.png
https://dahodan.johocen.com/wp-content/uploads/sites/50/2022/08/chrome_CHtWda1c0H.png

Hi @mubiesam,

The only way I could see to move forward is to rule out where exactly the CSS is getting overridden.

Since clearing cache isn’t making any difference, this could also be due to a conflict. Could you please try running a conflict test to double-check whether you could replicate the same issue if you temporarily deactivate all the plugins except Forminator and switch to a default WP Theme?

If you happen to notice it’s working fine after the above, it would mean the existing theme or the plugin is overriding the CSS.

Please check the following flow chart on how to run a conflict test:
https://wpmudev.com/wp-content/uploads/2015/09/Support-Process-Support-Process.gif

Please do let us know how that goes so that we can check further if needed.

Kind Regards,
Nithin

Hi Nithin @wpmudevsupport11

I had used “Freesoul Deactivate Plugins” to Deactivated all the Plugins, and even changed the theme to 2021, but still got the same result as screenshot

But it seems that Forminator is the only plugin which can not be detected by “Freesoul Deactivate Plugins”, see screenshot

Any other possibility?
Thanks

Hi @mubiesam

Freesoul Deactivate Plugins should not have problems in detecting Forminator.
I’ve right now tested it.
Have you refreshed the backend page of Freesoul Deactivate Plugins.
Try also to deactivate Freesoul Deactivate Plugins and activate it again. Then refresh the page. Be careful, you have only to deactivate it, NOT DELETE IT. If you delete it you will lose all the settings.
Deactivating and activating again FDP will clear the internal cache of FDP.

If you still have issues don’t hesitate to open a thread on the support forum of FDP. I’m the author.

Best regards

Jose

Hi Jose @giuse

It’s kind of strange as you can see on this screenshot, Forminator is activated on the left menu, but not listed in the right side as the activated plugins.

Meanwhile, when I deactivated FDP, a warning message is showing, is it because my installation is a multisites?

Freesoul Deactivate Plugins is not active, but its mu-plugin was not deleted.

Normally, when you deactivate FDP, it automatically deletes its mu-plugin file.

If you still have that file, it means you disabed FDP via FTP or something went wrong during the deactivation process.

Delete the file wp-content/mu-plugins/eos-deactivate-plugins.php if you want to completely disable FDP.`

Thanks

Hi @mubiesam
Yes, you have these issues because it’s multisite.

If you have a Multisite installation, on every single site you will be able to manage only the plugins which are active on that site. Freesoul Deactivte Plugins will not see those plugins that are globally active in the Network. And you have to activate FDP on every single site, not globally on the Network.

Let’s clarify it with an example, on the entire network you have plugins A, B, C, D, E, F, and G. And you have the websites Site1, Site2, Site3.

Freesoul Deactivate Plugins must be not active on the network. If you need it on Site1, you activate it on Site1. I think you are already doing that.

Imagine on the network you have activated plugins A, B, D. On Site1 you have activated Freesoul Deactivate Plugins and plugins A, E, F.
Well, on Site1 Freesoul Deactivate Plugins will see only plugins A, E, and F. It will not see B and D.

Probably Forminator is active on the entire network. This is why FDP doesn’t see it. It assumes that if you have activated it on the entire network it’s a plugin that you want everywhere.

About the message that you see when you deactivate FDP, this is something that should be improved, but it’s also due to the Multisite installation.
I know why you see that message, but It’s a little complicated to be explained.
You can ignore that message.

I would not like to invade the support forum of another plugin. If you need more help feel free to open a thread on the support forum of Freesoul Deactivate Plugins. I will be happy to help you there.

Best regards

Jose

Hi @mubiesam

I hope you are doing well.

Can you please try this stronger CSS:

.page-id-270 .forminator-ui#forminator-module-362.forminator-design--default .forminator-file-upload > span {
    color: #fff !important;
}

In WordPress > Appearance > Customise > Additional CSS instead?

For Freesoul plugin you can create a new ticket here

Best Regards
Patrick Freitas

Hi Patrick @wpmudevsupport12

This stronger CSS works as expected.

Thanks for your help.