RoseHosting

Do you have access to a control panel? You should have if you are using shared hosting.

If so, you can use phpMyAdmin to reset the password. It is a web-based tool to manage the database. Follow the instruction at https://codex.www.ads-software.com/Resetting_Your_Password about how to reset the password through phpMyAdmin.

You should be able to install wordpress in the https://example.com/blog and https://example.com/art subdirectory. There is nothing wrong with that setup.

https://blog.example.com is a subdomain but https://example.com/blog is not a subdomain.

Most likely this is a custom plugin using the Featherlight lightweight jQuery lightbox script.

If you have SSH access to your server you can navigate to the wp-content/plugins/ directory and delete the jetpack plugin directory. You can also delete the jetpack plugin directory through FTP/SFTP if you do not have SSH access. After you delete the jetpack plugin directory, you can install it again through your wordpress dashboard.

You can try to set the Site URL manually. Open the wp-config.php file and add:

define('WP_HOME','https://localhost/domain-name');
define('WP_SITEURL','https://localhost/domain-name');

If you are running an older wordpress installation, upgrading your wordpress core to the latest version available should fix the problem.

Even if WP_DEBUG is set to false, you may have a php.ini that’s overriding error displays.

It doesn’t make any significant difference if WordPress is installed manually or by using Softaculous. It is a matter of personal preference.

Softaculous doesn’t store any additional files in the document root for the website. The user data is stored outside of this directory, so unless your cPanel account is compromised, the Softaculous data will be safe.

It is good to know that Softaculous will save you both a lot of time and effort especially if you are not experienced with manual installations.

Esmi is right. Free web hosting is inviting trouble for your websites and it is very bad especially if you use them for your livelihood. You should use free hosting for testing purposes.

We offer One-Click-Install hosting where you can install unlimited (as disk permits) number of WordPress websites using one click.

Check the plans we offer here.

Feel free to contact us via chat or ticket if you need more info.

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

In most cases slowness in WordPress (especially the backend) is experienced due to many plugins and themes, not using a cache mechanism or a slow host and connection.

Before contacting your host, try to remove the unnecessary plugins and themes, install W3 Total Cache and use a CDN for the website.

If that doesn’t resolve the problem, contact your host.

You should be able to access the WP installation at: https://www.oldwp.com/newwpsubdir/ not https://www.oldwp.com/newwpsubdir/wp-admin/install.php)

Don’t forget to check your web server log files when troubleshooting issues related to it.

You might want to check your .htaccess file and double-check your WordPress files/directories permissions and ownership.

If you don’t know how, contact your host.

If I understood you correctly, then you need to change your site URL.

This can be done differently, from the WP dashboard, by editing the wp-config file, modifying the database or via wp-cli.

The easiest method is from your WordPress dashboard.

You can find more info at: https://codex.www.ads-software.com/Changing_The_Site_URL

You should check your Nginx error/access log file or the respective website log.

The answer to a problem lies in figuring what the actual problem really is.
And that will happen if you investigate this further.

Also, are you certain that the files/directories are under Nginx ownership?

If you have access to your server log files, then we advise you to check the log file that is configured for your website in the respective web server configuration file.

By the way you described the problem it seems that there are missing WP files/directories in place. You can download a fresh WordPress installation and try again.

However for troubleshooting it is better if you check the log files.

Sometimes this error can happen if you are exhausting your PHP memory limit, so create a file to your ‘wp-admin’ directory called php.ini and add the following line to it:

memory=64MB

Also, double-check the .htaccess file in your website root directory and make sure it contains the following lines:
# 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