Dat Hoang

Well, it looks like you got what you want with this code?

.jetpack_subscription_widget #subscribe-email input, .jetpack_subscription_widget input[type="submit"] {
color: #666666 !important;
background-color: #eeeeee !important;
}


Screenshot: https://take.ms/oZ2ii

If so, you should confirm this and mark this resolve ??

You should not install any plugin more. That’s my opinion.

Instead, you should follow one of my advised plugins above.

Their purposes: change all https://www.stijnspreekt.nl/ (http) links to https://www.stijnspreekt.nl/ (https) links.

I hope that does help.

See my attachment https://take.ms/YQwtV

You see that there is a CSS file that can be loaded.

Try to clear your cache and minified CSS files and see that does help?

—

Based on what you described, that seems not enough to change site from http to https. There are some records on your database, you need to change this as well.
I suggest 2 plugins:

1, https://www.ads-software.com/plugins/better-search-replace/ – Change all http to https links
2, https://www.ads-software.com/plugins/duplicator – create a package, clone it with the new domain “https”

Let me know if this does help ??

• This reply was modified 8 years, 3 months ago by Dat Hoang.

See my attachmenthttps://take.ms/YQwtV

Issue:

(index):1100 Mixed Content: The page at 'https://www.stijnspreekt.nl/8-tekenen-dat-een-man-serieus-is-en-je-echt-leuk-vindt/' was loaded over HTTPS, but requested an insecure stylesheet 'https://www.stijnspreekt.nl/wp-content/cache/autoptimize/css/autoptimize_f6be90334efab7ca5ef78a90f3c7f4a0.css'. This request has been blocked; the content must be served over HTTPS.


The CSS style is blocked.

====

Please try to delete your cache and let’s see?

However, based on what you’re descsribing, it’s not enough to move HTTP to HTTPS. There are something you need to change in your database as well.

I suggest following either ways:
1, Use https://www.ads-software.com/plugins/duplicator/ . Make a package, re-install it and change the site URLs to https

2, Use https://www.ads-software.com/plugins/search-and-replace/ . Change your site URL from http to https.

Tell me if anything does help ??

If so, follow these:

* Use git to check the changes in your site, to know which files are getting changed.
* Compare the database in the case the virus is getting back.

Do you notice any change?
I’m not sure but it seems you don’t know about GIT? It’s more than just “how to find files that have been altered and to remove code changes.”


I would like to know if there is a way to eliminate the ability to login to the dashboard completely by deleting wordpress files.

Based on what I know and what you already described, this is not possible in your case.

OK. That’s all my thoughts here ?? . If these do not help, wait for other replies.

I think you should check with your hosting support.

Another idea has just come across my mind: your hosting space is full?

It looks like your site can not load some CSS files correctly.

There are some questions to make this clear.
1. What is the link to your site?
2. How did you do this Today i migrated from HTTP to HTTPS.?

Another suggestion is to use the browser consoles to check:
* https://developers.google.com/web/tools/chrome-devtools/console/
* https://developer.mozilla.org/en/docs/Tools/Browser_Console

That’s possible.

a specific directory with 70 files in it


“Directory” means “categories”, right?
And “70 files” means “70 posts”?

If I understand correctly, so you want to apply this code to this category page, or to 70 posts having this category?

hi, can I have a link to your site?

Based on what you said, it looks like that the hacker has the higher level in his/her attack. If so, these plugins may not help. I think they’re good at to “prevent”, but not enough to “fix”.

The ideas of checking your issue include:

* Re-install all files including WordPress core, themes and plugins with the same current versions.
* Use git to check the changes in your site, to know which files are getting changed.
* Compare the database in the case the virus is getting back.
* Change all weak passwords (database, FTP, admin accounts) and make them strong.
* Apply other practices like restricting access to the area of wp-admin, chmod for the specific locations.

If you are unfamiliar with the terms I’m talking above, it would be better to hire someone rather than struggle with it by yourself.

You can look at the browser consoles to see what the exact issue is:

* https://developers.google.com/web/tools/chrome-devtools/console/
* https://developer.mozilla.org/en-US/docs/Tools/Web_Console

That might suggest what the issue is.

For the social links and “My account”, I think you should follow this https://docs.woocommerce.com/document/create-a-social-icon-menu/

Or you still want to stick with “before” and “after” your logo. You can use this code:
https://gist.github.com/htdat/6d8d7201430890699d6a19ee2ea6af8a (you should use this one)


add_action( 'storefront_header', 'htdat_above_logo', 15 );
function htdat_above_logo() { ?>
<div style="clear: both; text-align: left;">
<span style="margin: 0 0.5em;">Facebook!</span>
<span style="margin: 0 0.5em;">Twitter!</span>
</div>
<?php
}
add_action( 'storefront_header', 'htdat_below_logo', 41 );
function htdat_below_logo() { ?>
<div style="clear: both; text-align: left;">
<span style="margin: 0 0.5em;">My account</span>
<span style="margin: 0 0.5em;">Register!</span>
</div>
<?php
}


This code is based on https://docs.woocommerce.com/document/add-static-content-to-the-storefront-header/

• This reply was modified 8 years, 3 months ago by Dat Hoang.
• This reply was modified 8 years, 3 months ago by Dat Hoang. Reason: well, too bad to handle the code

To remove the search box, you can use this code:

remove_action('storefront_header', 'storefront_product_search', 40);


It’d be better to follow this https://github.com/woocommerce/theme-customisations

Photo lightbox? This is a default feature of WooCommerce, or this feature is from another plugin?

I suggest disabling your plugins one-by-one and see which plugin is causing the issue.

More advanced, you can look at the browser consoles to see what the exact issue is:
* https://developers.google.com/web/tools/chrome-devtools/console/
* https://developer.mozilla.org/en-US/docs/Tools/Web_Console

It looks like your question is unclear?
You can have a screenshot in which you should put some arrows and texts to show your need clearer.