These are notes and observations made during the socialremediation.com installation.
The server is a Plesk system, initially I set up FTP but it did not work so I proceeded using the Plesk File Manager, later when I returned to the install to upload content, the FTP was working.
It seems there are delays in the Plesk system when system criteria are modified.
Install _Kudoseo package to Client WebServer
Download, unzip and install the kudoseo to the template directory of the client website.
Upload the package to the client webserver.
Then …
Insert the Install paths into the _kudoseo/config.php
- There is one path for the directory that host _kudoseo - KUDO_PATH. It is to be entered without the domain name ie: only the path. eg: define(“KUDO_PATH”,“dir/path/to/kudoseo/?”);
It must start with NO leading Slashes (/) and end with a trailing slash and a question mark (/?).
- There is the $_SERVER['SERVER_NAME'] if the client domain name begins with (www.). This line may need to be UnRemmed and the value changed to reflect the clients naked domain-name.com. It is a good idea to set this rather than just leave it up to php and the server.
Go into the client template and at the php level : include('dir/path/to/kudoseo/'.'sem-content.inc.php');
Set Paths for the SEM VARS that kudoseo exposes to php and are to be inserted into the clients website template.
$GLOBALS['sem_title_meta'] - checks sem-content : goes in the header.php template around where <title> is inserted in the template
$GLOBALS['sem_connections'] - checks sem-content : goes in the header.php template - html-doc after all javascript calls before the closing </head> tag.
$GLOBALS['sem_keypress'] - checks sem-content : goes in the <body> tag
$GLOBALS['sem_content'] - goes within the html-doc itself, on-page prominently placed near the <nav>
$GLOBALS['sem_footer_link'] - checks sem-content : goes in the footer.php part of the template.
Install Client to _kudoseo database
* Create the Password
-
http://www.xkpasswd.net.
Use this config which generates nice passwords { “num_words”: 3, “word_length_min”: 4, “word_length_max”: 8, “case_transform”: “CAPITALISE”, “separator_character”: “RANDOM”, “separator_alphabet”: [ “!”, “@”, “$”, “%”, “^”, “&”, “*”, “-”, “_”, “+”, “=”, “:”, “|”, “~”, “?”, “/”, “.”, “;” ], “padding_digits_before”: 0, “padding_digits_after”: 2, “padding_type”: “NONE”, “random_increment”: “AUTO”}
* Create the username - which is an imaginary mailbox(which could be real if needed) eg: kudoseo@socialremediation.com
* Set the path that you Installed the kudoseo package to in the clients config.php
KUDO_PATH. Leave out the domain name
http://socialremediation.com/ - we just want the PATH from the Root Domain/
PATH/_kudoseo/
eg:
“/wp-content/themes/client-theme-name/_kudoseo/?” it must finish with (?)
Create Verify Directories and Client JSON storage
* In kudoseo.com/cli/ create a directory in the clients domain name without any www.prefix
* copy in the accstat.json array
{“domain”:“naked-clients-domain-name.com”,
“status”:true,
“kdc”:“
http://kudoseo.com/cli/”,
“kds”:“
http://kudoseo.com/maas/?”,
“jsr”:“/lib/SeoJsonReader/SeoJsonReader.php”,
“kdp”:“/data/ffdb.json”,
“message”:“Kudoseo services under normal supply.”,
“hits”:“9999”}
The accstat.json file must remain in the Root as the installed _kudoseo instance will look for the file whenever the cleint website receives a request !
* Create a directory for the current year - this will be for storage of dated versions of client json database files eg: 20160725@14.24.16.json
The JSON Editor should connect to the kudoseo flat-file json database located on the client server and allow editing and saving.