wayneconnor

AS I’ve said above,
I’ve re-enabled jetpack temporarily as currently the ONLY was I have of doing any admin like approving comments is via WordPress.com interface which uses jetpack.
But when I disable jetpack (the only plugin I have running) I still get the error.

It gives no errors.

It just redirects to login screen.

I have no .htaccess in wp-admin folder

This is my normal htaccess:

BEGIN WPSuperCache END WPSuperCache

RewriteCond %{HTTP_COOKIE} !^.278e57c767f1e56591558d90db368060.$
RewriteCond %{REQUEST_URI} !^/.well-known/acme-challenge/[0-9a-zA-Z_-]+$
RewriteCond %{REQUEST_URI} !^/.well-known/cpanel-dcv/[0-9a-zA-Z_-]+$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/(?:\ Ballot169)?
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?:\ Comodo\ DCV)?$
RewriteRule ^wp-comments-post.php – [F,L] AddHandler application/x-httpd-ea-php56 .php

RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301] BEGIN WordPress The directives (lines) between “BEGIN WordPress” and “END WordPress” are dynamically generated, and should only be modified via WordPress filters. Any changes to the directives between these markers will be overwritten.

RewriteEngine On RewriteRule .* – [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}] RewriteBase / RewriteRule ^index.php$ – [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] END WordPress php — BEGIN cPanel-generated handler, do not edit Set the “ea-php74” package as the default “PHP” programming language.

AddHandler application/x-httpd-ea-php74___lsphp .php .php7 .phtml php — END cPanel-generated handler, do not edit

Thanks,

I’ve done this.
With ALL plugins disabled and ALL themes disabled I still cannot login.
I have temporarily enabled the Jetpack plugin as I am using it to try to backup my site.

It is detecting right tor wrong login password.
Right password redirects to front page again.

Thanks, I’ve logged a request with jetpack.
Yes I renamed the theme folder.
I also used phpmyadmin to change the theme to twenty-twenty.

I have re-enabled plugins and themes so my site at dubbo.org is actually working.
And I have some minimal control from wordpress.com
It gives the correct ‘count’ of my posts (89) but says “You havn’t created any content yet”

And I cannot log into the admin.
If I try ‘write post’ from wordpress.com I get:

Deprecated: Hook jetpack_check_mobile is deprecated since version jetpack-8.3.0 with no alternative available. in /home4/machostc/public_html/dubbo/wp-includes/functions.php on line 6031

Warning: Cannot modify header information – headers already sent by (output started at /home4/machostc/public_html/dubbo/wp-includes/functions.php:6031) in /home4/machostc/public_html/dubbo/wp-includes/pluggable.php on line 1435

Warning: Cannot modify header information – headers already sent by (output started at /home4/machostc/public_html/dubbo/wp-includes/functions.php:6031) in /home4/machostc/public_html/dubbo/wp-includes/pluggable.php on line 1438

I can’t remember why I cut out that functionality. It was 8 years ago or so.
It took me a lot of hours to get it working – getting the headings generated on the fly – it was clever and tricky and took a lot of trial and error – and I was pleased with it – so I would not have removed it lightly.

My gut reaction is that something might have changed in WordPress (maybe with the release of WordPress 3???) that made it impossible for me to continue generating the headings on the fly so I had to go back to the old way of doing it

But honestly, I can’t remember it was so long ago.

Great to hear!

I haven’t heard about that, but is it possible to try a different plug-in?
What does portfolio manager plug-in do?

Great!

Go to theme options and de-select the option to ‘open slider’ on current page.

Because you are starting completely fresh on the new WordPress host, I would say export your old posts, import them into the new WordPress, and download a fresh version of sliding door onto the new WordPress hosting account. You can then play around with it and try and get it looking like you would like it to.

If you decide that there were too many customisations on your old site and you’d like to go back to that older version of sliding door, you can just delete the newer version of sliding door from the new host and copy across the old version from your other server.

But over the years there have been lots of upgrades to the theme so I think you will be happier with the newer version.

You are in a good position to play around with the new theme on the new server because you still have a complete backup on your old server.

• This reply was modified 8 years, 1 month ago by wayneconnor.
• This reply was modified 8 years, 1 month ago by wayneconnor.

I forget how this works, but I think if you are open to the page then the menu for that page will be full width.
So if you link the first menu to something other than the home page of your website that should fix that problem. It’s been a little while since I fiddled with this theme so I can’t remember!

Can anyone else remember how to do this?

The latest version of the theme is compatible with the latest version of WordPress.

If you are using a version of WordPress newer than WordPress 4.4 then you have to make sure you are using a version of the sliding door theme newer than 3.2.2.

In all cases this will be resolved if you simply make sure that your WordPress is updated to the latest version ( which it always should be) and that the theme is also upgraded to the latest version ( which it also should be).

Also you must test on multiple browsers.