RossMitchell

Suggest that you report this in the support forum for the site health plugin.

This is what I do. I grant that it is possible to do some of the steps a little simpler, but the saving is limited, and detatches you from some of the basic toolset.
So if you don’t have an FTP program called FILEZILLA then get it and install it now. Setup the FTP or SFTP website access in filezilla.
– First you need to register your new domain name. I always register my domains at a distinct company from the hosting company, it gives me a bit more control if things go wrong technically or commercially.
– At your hosting company, set the nameservers as advised by your hosting company, some hosting setups require the nameservers to be set before they will accept an addon domain.
– At your hosting management set your addon domain, and nominate a new directory in your webserver root directory to receive the domain name mapping. Your primary domain maps to “public_html”, the addon tool will probably offer a subdirectory in public_html, but resist this default and remove the public_html part.
– Optional, configure the letsencrypt SSL certificate.
– Download the ZIP archive of WordPress files, expand it on your computer.
– On your website database manager (probably phpmyadmin), create your new database and also create a database user and password, make these distinct for each WordPress setup you install, don’t compromise the security and isolationm of your sites by sharing these. Keep a record of these.
– In your WordPress files, make a copy of the wp-config-sample.php file as wp-config.php, put the database name, database user and password into the config file. Optionally set the salt strings.
– Using FILEZILLA connect to your webserver and upload all of your WordPress files.
– Test your install by browse to: http://your new domain/readme.html
if it does not display then you have a problem you need to fix.
– Activate your WordPress install by browsing to:
http://your domain/wp-admin/install.php
or possibly https
follow the instructions.
– Optional password protect your website so that only you and people you authosise can see your new install.
– Install plugins and themes.

Most of these steps are covered in more detail here in the 5 minute install instructions
http://codex.wordpress.org/Installing_WordPress

Yes, updating your WordPress is an excellent aspiration, but I would not expect it to fix your problem.
One possibility is that the hackers are accessing your “xmlrpc.php” file.
Suggest that you look at the database “user” table and see exactly when these users are created. Go to your website access logs and find the entries that match these times.
What you find should direct your next steps.
Maybe you can block their IP address, block access to xmlrpc.php

You need to use your browser inspector to see how your website is using its CSS and HTML. Each browser has a browser inspector.
Once you have identified which aspects of your layout you want to adjust, the browser inspector will show you which elements are involved, and how the layout is being done, like is it margins or padding, etc.
Then you can use the WordPress Customizer> Additional CSS page to adjust the CSS.

If you had given us your real website URL rather than a screenshot, then someone here would have been able to give you specific instructions rather than the general principles I have.

• This reply was modified 5 years, 1 month ago by RossMitchell.

Very tidy.
If you have resolved your issue, could you mark this thread as resolved.

If it is not in appearance > widgets, then I would suggest that you look in your theme customisation.
Most likely in “salmon-child” you will find a file “footer.php”
Or someone may have used a hook or filter, most likely in your child theme.

Otherwise use your browser inspector to find the CSS and HTML and text associated with your footer paragraphs, and search your files (themes and plugins), and database for them.

• This reply was modified 5 years, 1 month ago by RossMitchell.

The two shortcodes are sharing the same object of class Shortcode_Handler, it has two fields which are updated in the foreach loop in your function cld_add_custom_shortcode, hence when the shortcodes get invoked only the last set values are there.
You need to create a new object for each shortcode and pass this distinct object into the add_shortcode function. This way the shortcode name is paired with an object that remembers the fileds for that shortcode.

It is risky to edit your code like this, but I will try.
Note that the variables are now public.

<?php 
/**
 * The shorcode handler class
 */
class Shortcode_Handler {
  public $field_array;
  public $form_id;

  public function cld_generate_form() {
    // Get form fields
    $fields = $this->field_array;
    $form_id = $this->form_id;  
    $form = '<form id="'.$form_id.'" method="post">';
    foreach ($fields as $value) {
      $form .= '<input name="'.$value.'" value="" />';
    }
    $form .= '<input type="submit" name="submit">';
    $form .= '</form>';
    return $form;
  }
}

/* register the shortcodes */
function cld_add_custom_shortcode() {
    global $wpdb;
    $table_name = $wpdb->prefix . 'options';
    $results = $wpdb->get_results("SELECT * FROM $table_name WHERE option_name LIKE '%cld_form_id-%'");
    foreach ($results as $value) {
      $shorcode_tag_name = $value->option_name;
      $sc_object = new Shortcode_Handler;
      $sc_object->form_id = $value->option_name;
      $sc_object->field_array = maybe_unserialize($value->option_value);
      add_shortcode($shorcode_tag_name, [$sc_object, 'cld_generate_form']);
    }
 }

  add_action('init', 'cld_add_custom_shortcode');

Suggest that you install your themes and plugins manually in your hosting files. This saves you from addressing the difficulties of getting your file ownership and permissions right, that are required to let the webserver mediated file updating.

Download the theme or plugin in a ZIP file, extract it and cut/paste the directory into the wp-content sub-directories.