khoavo

@rankbrands – I know but it’s been running fine up to WooCommerce v8.40. Not sure why WC v8.5.1 is causing this issue. I noticed some other users are experiencing the same issue (503 error, etc) when they installed WC v8.5.1. Been using Shared Hosting forever and no need to get dedicated hosting you know?

Okay guys, please start a new support ticket and thread. Appreciate your input and feedbacks, but I need to stop getting notifications on this ticket, it’s bee closed. Thanks.

(@c8rls) – No problem. I’m sure the developer will come up with a new fix soon for the logo issues, etc. I’ve been using this plugins for years and it’s one of the best ones out there, and they do a good job supporting. There’s not perfect plugin, but this one is more than good enough for me to use.

(@c8rls) To vertically center it, add the CSS below in LoginPress / Customizer / Custom CSS/JS box. I’m not having issues with the Logo, everything is still good after the latest LoginPress update and switching to the Default theme.

/* Login Form – Vertically center it on the browser window */
body.login {
display: block !important;
} login {

  position: absolute !important;
  top: 50%;
  left: 50%;
  transform: translate(-50%, -50%);
  margin-top: 0 !important;

}

Ahhhh, now I see. Thanks to all you guys and (@abdulwahab610) – Excellent customer support. Have a great day!

(@dcutting) Switch what theme? LoginPress theme? or WordPress Theme? I was hoping to not have to switch anything and leave all of my current setting and CSS as they are after the plugin update. So waiting for the developer to apply a new fix. Thanks for the input.

(@abdulwahab610) – Negative, v3.0.1 didn’t solve it, I still see the same layout issues after the latest update. I tried it on couple different WordPress sites. So I had to revert back to v1.8 again until a fix is available. I still think your plugin is one of the best ones out there for this purpose, but it just need a global fix on this layout issue. Thanks.

Never mind, issues solved. I discovered another plugin was causing the conflict, so I adjusted its settings. All good now. Thanks for sharing your valuable popup login plugin.

Yeah I start updating some of my client’s sites, until I noticed the issue so I stopped with updating the rest of the sites. Hopefully they can provide a global six for this.

Thanks

Yeah I have another site on the same server that also experiencing the same scan timeout issues. I think my web hosting doesn’t have enough PHP memory overall as it’s only 512MB.

Well thanks for your help anyhow. I’ll just ignore these scam timeout notifications in the future.

Firewall on my web host? Not that I’m aware of, just the standard Shared Hosting Evironment.

I did as you instructed. First, saw this error message: https://prnt.sc/iUKXpa0ycOpa

Here’s the last 20 lines from the Log:

• [Mar 23 15:34:33] Scanning: /hermes/bosnacweb05/bosnacweb05/bosnacweb05ay/b700/ipw.pumacomm/VamosCuba_Group/wp-content/plugins/elementor/core/common/modules/finder/categories/create.php (Mem:91.0M)
• [Mar 23 15:34:33] Scanning: /hermes/bosnacweb05/bosnacweb05/bosnacweb05ay/b700/ipw.pumacomm/VamosCuba_Group/wp-content/plugins/elementor/core/common/modules/finder/categories/edit.php (Mem:91.0M)
• [Mar 23 15:34:33] Scanning: /hermes/bosnacweb05/bosnacweb05/bosnacweb05ay/b700/ipw.pumacomm/VamosCuba_Group/wp-content/plugins/elementor/core/common/modules/finder/categories/general.php (Mem:91.0M)
• [Mar 23 15:34:33] Scanning: /hermes/bosnacweb05/bosnacweb05/bosnacweb05ay/b700/ipw.pumacomm/VamosCuba_Group/wp-content/plugins/elementor/core/common/modules/finder/categories/settings.php (Mem:91.0M)
• [Mar 23 15:34:33] Scanning: /hermes/bosnacweb05/bosnacweb05/bosnacweb05ay/b700/ipw.pumacomm/VamosCuba_Group/wp-content/plugins/elementor/core/common/modules/finder/categories/site.php (Mem:91.0M)
• [Mar 23 15:34:33] Scanning: /hermes/bosnacweb05/bosnacweb05/bosnacweb05ay/b700/ipw.pumacomm/VamosCuba_Group/wp-content/plugins/elementor/core/common/modules/finder/categories/tools.php (Mem:91.0M)
• [Mar 23 15:34:33] Scanning: /hermes/bosnacweb05/bosnacweb05/bosnacweb05ay/b700/ipw.pumacomm/VamosCuba_Group/wp-content/plugins/elementor/core/common/modules/finder/categories-manager.php (Mem:91.0M)
• [Mar 23 15:34:33] Scanning: /hermes/bosnacweb05/bosnacweb05/bosnacweb05ay/b700/ipw.pumacomm/VamosCuba_Group/wp-content/plugins/elementor/core/common/modules/finder/module.php (Mem:91.0M)
• [Mar 23 15:34:33] Scanning: /hermes/bosnacweb05/bosnacweb05/bosnacweb05ay/b700/ipw.pumacomm/VamosCuba_Group/wp-content/plugins/elementor/core/common/modules/finder/template.php (Mem:91.0M)
• [Mar 23 15:34:33] Scanning: /hermes/bosnacweb05/bosnacweb05/bosnacweb05ay/b700/ipw.pumacomm/VamosCuba_Group/wp-content/plugins/elementor/core/debug/classes/htaccess.php (Mem:91.0M)
• [Mar 23 15:34:34] Scanning: /hermes/bosnacweb05/bosnacweb05/bosnacweb05ay/b700/ipw.pumacomm/VamosCuba_Group/wp-content/plugins/elementor/core/debug/classes/inspection-base.php (Mem:91.0M)
• [Mar 23 15:34:34] Calling fork() from wordfenceHash with maxExecTime: 20
• [Mar 23 15:34:34] Entered fork()
• [Mar 23 15:34:34] Calling startScan(true)
• [Mar 23 15:34:34] Got value from wf config maxExecutionTime: 20
• [Mar 23 15:34:34] getMaxExecutionTime() returning config value: 20
• [Mar 23 15:34:34] Cached result for scan start test: true
• [Mar 23 15:34:34] Starting cron with normal ajax at URL https://vamoscubagroup.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=1&scanMode=custom&cronKey=92ce3b7cd929393db5a813b7db624fd8&signature=fb71cc95209d0cce155208601247ba718ba69c2be46376e3259ff9c3090dffd4
• [Mar 23 15:34:36]?Scan process ended after forking.

I believe the php memory limit value is already set to the max. Where or how do I disable and enable the start scans remotely?

@japenz – Yup, works nicely. Much appreciate you! Thank you.