Page 4 of 4

Re: SideBar content shifts to bottom of page

Posted: 07 Jan 2017, 09:20
by nileda
What is the usual way?

Re: SideBar content shifts to bottom of page

Posted: 07 Jan 2017, 09:59
by Colin
I detailed it in my post

Go to Appearance > Themes etc in the WP dashboard.

If you are having this much trouble doing standard things to your site you may be better paying someone local to sort it for you.

Re: SideBar content shifts to bottom of page

Posted: 07 Jan 2017, 14:30
by nileda
Sorry to bother you gain, but when I go to
Appearance->Themes->Add New->Upload Theme->Choose File suffusion 4.4.9 Install Now
I get this
QUOTE Unpacking the package… Installing the theme…
Destination folder already exists. /home/exquisiteslave/public_html/wp-content/themes/suffusion/
Theme install failed. UNQUOTE
Thank you for your cooperation.

Re: SideBar content shifts to bottom of page

Posted: 08 Jan 2017, 00:19
by Colin
Delete Suffusion then using FTP or cPanel etc from your web host and then reinstall.

Again this is simple normal WP stuff and not anything to do with Suffusion. Try getting some local expert help.

Re: SideBar content shifts to bottom of page

Posted: 08 Jan 2017, 08:36
by nileda
I am confident that I am able to develop my website (5,696 posts, 12,491 pics) without paying some local expert help, as I have done for the last 3 years.
My webhoster has moved my website from Cpanel to Webmin in a dedicated stuff and it is hard, if not risky, to download/reinstall the .zip Suffusion 4.4.9 converted to RPM or the like: do you have a link to a Suffusion 4.4.9 reinstall package compatible with Webmin.
Thank you for your cooperation.

Re: SideBar content shifts to bottom of page

Posted: 08 Jan 2017, 10:31
by Colin
No that is the only version.

Given your comments I don't share your optimism but it is your site so continue how you wish BUT do learn a bit more about Wordpress and how it works.

Re: SideBar content shifts to bottom of page

Posted: 17 Jan 2017, 06:03
by nileda
Thank you, Colin, for your precious help.
The problem was due to a plugin, now updated, but was still there when the plugin was deactivated before the update.
Best,