bernbe01

hey there! looks like you got the “get a quote” page to honor the 1.7em line height, nicely done! out of curiosity, what did your fix end up being?

do you have any lingering issues at this time?

that is true that to use ftp you would need a separate program such as filezilla

if you are able to download your wordpress installation directory via file manager that would be acceptable, but learning to use ftp might prove useful in the long run, especially when we get to uploading the files and folders from the clean wordpress you downloaded

i suggest you search the help docs on your host’s site for how to use ftp, as they will likely have specific information for your environment

typically it is just andaddress, username, and password that is needed to begin with ftp

hey there!

it looks like you’ve made good progress on your site, but i see you still have a few content issues (images and links, etc)

the good news is i am able to browse the site without being logged in. is that functioning as you intend?

on this page, images in content appear broken:
https://mitgard.com/about-us/

you might be able to use a plugin to change content urls to help fix a bunch of these issues at once. velvet blue update urls is a trusted plugin by me for stuff like this

is there anything specific i can help you figure out?

hey there

i’m not sure of a plugin off hand for this but maybe if we talk it through we’ll come up with an idea together

what is the reason for this? it seems in order to process the payment you’d need much of the user’s info, so might they as well register?

is what you’re looking for the site to do pretty default to a guest checkout?

what checkout modules do you use in woocommerce (if any)

you’re doing awesome! no need for apologies

it could be a virus or a hack, thats why reinstalling your wordpress core is a good idea. a corruption in the files could have this affect too

for the backup, are you talking about step 0?

if yes, for now download all files via ftp

then following those instructions upload clean versions from the release archive for everything *except* wp-config.php and the wp-content folder

–> this will preserve your themes and plugins (which should all still be deactivated)

taking a backup of the database can be done via phpMyAdmin or mysql directly. in cpanel you usually can manage your databases, and inside of the phpMyAdmin option there is usually an Export tab which will allow you to download the current db to your computer

the backups are just a safety precaution

any change on the frontend?

if not do you mind trying to manually re-install version 3.5.1 from the release archive following the instructions above?

i don’t know if it’ll tell you anything new, but it may be worth trying this tool?

background updates tester

we’ve seen a few times where this couldn’t catch the issue lately, but usually it does

and if you dont want to use user id’s for your meta data delete, you can use a query like this, just know it is slower to use subselects

make sure you edit the usernames in the subselect to the ones you want to keep

DELETE FROM wp_usermeta WHERE user_id NOT IN(SELECT ID FROM wp_users WHERE user_login IN ('admin','second_user_to_keep','etc'))

hey there

do you have ftp access?

if yes you can find your wordpress version by opening wp-includes/version.php

i would start by deactivating plugins temporarily to confirm it is not an issue. using ftp, rename the folder wp-content/plugins to wp-content/plugins.HOLD

also revert your changes in wp-settings.php please

test. if no luck proceed to:

i think you’re going to need to manually re-install whichever version you are on if you do not want to go to current

i would suggest:

0. take a backup of your existing system (files & database – let me know if you need help)

1. download the your version of wordpress from the release archive

2. unzip it locally on your computer

3. connect to your server using an ftp client, selecting option to see hidden files if available

4. delete from your server everything in wordpress’s install folder except wp-config.php and wp-content/

5. upload from the newly unzipped wordpress files all files and folders except wp-content/ (there will not be a wp-config.php in the newly unzip wordpress)

hey there

a thought on this, are you able to access /wp-login.php or /wp-admin on the centos server?

if yes, try resaving your permalink structure (Dashboard->Settings->Permalinks) and take a look at the generated .htaccess file.

then i’d use a toold like diffchecker to compare each htaccess file. is the .htaccess file generated when you save permalinks on the centos box the same as the one on your MAMP server?

if you are unable to access /wp-admin, temporarily remove your .htaccess file and/or place the default settings from here in it

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

ok, since .htaccess is clean wp basic lines, plugins are disabled, basic clean theme has been tested, then i think it’s time to try a manual reinstall of the wordpress core files

to manually update wp 4.1.1

0. take a backup of your existing system

1. download the latest wordpress

2. unzip it locally on your computer

3. connect to your server using an ftp client, selecting option to see hidden files if available

4. delete from your server everything in wordpress’s install folder except wp-config.php and wp-content/

5. upload from the newly unzipped wordpress files all files and folders except wp-content/ (there will not be a wp-config.php in the newly unzip wordpress)

so on your site i see this file:

https://timcroughfit.com/wp-content/themes/personal-trainer/js/custom.js?ver=1.0

which is part of your theme is erroring out when viewed mobile on line 198. the error is present for both mobile and desktop, but is apparently not render blocking on desktop

i suggest testing the menu item as # on the twenty-fifteen theme. if that renders mobile then you might want to file a ticket at the theme’s support forum (a link to their support is available on this page)

the other thing to test, while still in twenty-fifteen, deactivate all plguins and retest the # link url

what about using

javascript:;

as the link url?

want to send a link to your site over? i’d be happy to make sure there isn’t something else going on

i dont think the # should break mobile nav so it may be worth trying

-deactivate all plugins
-revert to twenty-fifteen
-retest mobile menu entries