The official WordLift Web Site: wordlift.it

bash bin/install-wp-tests.sh wordpress_test root '' localhost 3.8

http://git-scm.com/book

We use Semantic Versioning. We add the SNAPSHOT suffix to releases that are not yet usable.

We try to stick to the WordPress coding standards as much as possible.

To join development you first need an account on Redlink with an Application Key. Follow these steps to get one:

• Register an account on my.redlink.io and login
  • from the datasets section, create a custom dataset
    • then release the dataset to yourself in RDFS format
    • publish the dataset
  • from the analyses section, create an analysis, then configure it with the following components:
    • input, use plain text
    • languages: select the expert language pack
    • datasets: select the dataset you created earlier and dbpedia and freebase
    • post-processing: select entity co-mention and dereference entities
    • outputs: choose RDF output
  • apply changes to the analysis settings by clicking the Apply button
  • from the applications section create an application, then bind
    • the dataset you created earlier
    • the analysis you created earlier
  • take note of the Application Key and of the User ID (the user ID appears in the dataset base URI, e.g.: http://data.redlink.io//).

Get the code and set-up a WordPress instance:

• Clone the code to a folder: git clone https://github.com/insideout10/wordlift-plugin.git
• from a WordPress instance, create a symbolic link to the plugin src folder: ln -s wordlift-plugin/src wordpress/wp-content/plugins/wordlift

Edit the wp-config.php file of your WordPress instance and set the debug mode. We use to write the log to the wp-content/debug.log file - see Example wp-config.php for Debugging:

// Enable WP_DEBUG mode
define('WP_DEBUG', true);

// Enable Debug logging to the /wp-content/debug.log file
define('WP_DEBUG_LOG', true);

// Disable display of errors and warnings
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors',0);

// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
define('SCRIPT_DEBUG', true);

As stylesheets and scripts files are part of the wordlift-plugin-js project, you need configure Apache to get these files.

NameVirtualHost *:80

<VirtualHost *:80>
	ServerName wordpress380.localhost

	RewriteEngine on

	DocumentRoot /var/www
	DirectoryIndex index.php

	# Preferred method, direct linking.
	AliasMatch ^/wp-content/plugins/wordlift/(css|fonts|js)/(.*)$ <your-folder>/wordlift-plugin-js/dist/3.0.0-beta/$1/$2
	<Directory ~ "<your-folder>/wordlift-plugin-js/dist/3.0.0-beta/(css|fonts|js)">
		Options All
		AllowOverride All
		order allow,deny
		allow from all
	</Directory>

	<Directory /var/www>
		AllowOverride All
		Order allow,deny
		Allow from All
	</Directory>

</VirtualHost>

This is especially useful if the WordLift scripts and stylesheets are hosted elsewhere:

NameVirtualHost *:80

<VirtualHost *:80>
	ServerName wordpress.localhost

	RewriteEngine on

	DocumentRoot /var/www
	DirectoryIndex index.php

	<Location ~ "/wp-content/plugins/wordlift/(css|fonts|js)/(.+)$">
		ProxyPassMatch http://localhost:8000/app/$1/$2
	</Location>

	<Directory /var/www>
		AllowOverride All
		Order allow,deny
		Allow from All
	</Directory>

</VirtualHost>

Before being able to run tests, you need to copy the file setenv.sh.dist to setenv.sh and set all the required parameters.

Run the test using the following command line:

WP_TESTS_DIR=wp-tests WP_VERSION=3.9.2 WP_MULTISITE=0 \
	API_URL=https://api.redlink.io/1.0-BETA \
	REDLINK_APP_KEY=<your-redlink-application-key> \
	REDLINK_USER_ID=<your-redlink-user-id> \
	REDLINK_APP_NAME=<your-redlink-application-name> \
	REDLINK_DATASET_NAME=<your-redlink-dataset-name> \
	WL_DISABLE_SPARQL_UPDATE_QUERIES_BUFFERING=true \
	php -d xdebug.profiler_enable=1 vendor/bin/phpunit