This repository was archived by the owner on Oct 3, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathreadme.txt
170 lines (99 loc) · 3.94 KB
/
readme.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
=== Debiki Wordpress Comments ===
Contributors:
Donate link:
Tags: comments
Requires at least: 3.4.2
Tested up to: 3.5
Stable tag: 3.5
License: GPLv2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html
A hopefully better commenting system that contributes to fruitful
discussions. Main features: Comment ratings and a two dimensional layout.
== Description ==
See http://wordpress.debiki.com/
== Installation ==
1. Unzip `debiki-wordpress-comments.zip` in the `/wp-content/plugins/` directory.
1. Activate the plugin through the 'Plugins' menu in WordPress
== Frequently Asked Questions ==
There are no frequently asked questions, as of right now.
You could ask questions here though:
http://wordpress.debiki.com/forum/
== Screenshots ==
Have a look at this page instead: http://wordpress.debiki.com/demo-1/
(There are no screenshots, as of right now.)
== Changelog ==
= v0.00.01 =
* Initial release (January 2013).
== Upgrade Notice ==
= v0.00.01 =
This is the initial release.
== Building ==
(Please have a look at LICENSE.txt: there's no warranty.)
To compile, minify, and combine Javascript and LiveScript, you need to install
Node.js and Grunt. Here follows instructions on how to do this, with Ubuntu
Linux and CentOS.
(If you're using another operating system, have a look at:
https://www.google.se/search?q=install+nodejs )
To build Node.js you need a C compiler, so first:
$ sudo aptitude install g++ git # for Ubuntu Linux
$ sudo yum install gcc-c++ make git # for CentOS
Now, install Node.js:
$ git clone https://github.com/joyent/node.git
$ cd node/
$ git checkout v0.8.16 # or perhaps some more recent version
$ ./configure
$ make
$ sudo make install
Then install Grunt, and nodejs dependencies:
$ sudo npm install -g grunt # see http://gruntjs.com/
(But on CentOS I had to do this:
$ sudo /usr/local/bin/npm install -g grunt
)
$ npm install # installs Node and Grunt dependencies
Now you can bundle JS and CSS files like so:
$ grunt
Now you're done. Run `grunt` whenever you've edited JS and CSS files, for
the changes to take effect.
== Testing ==
1. Install PEAR and PHPUnit
Install PEAR:
Install version >= 1.9.4, because earlier version(s) are broken and won't work
with PHPUnit. See: http://stackoverflow.com/a/8952814/694469
Many Linux/Mac distros ship the broken version, it seems. (My did.)
If you need to uninstall the old broken version:
$ sudo apt-get purge php5-pear # with Ubuntu Linux.
# Or simply `... purge php-pear`.
Installation instructions:
http://pear.php.net/manual/en/installation.getting.php
This worked for me: (I'm using Ubuntu Linux)
$ wget http://pear.php.net/go-pear.phar
$ sudo php go-pear.phar
Configure PEAR: (I think `sudo` is needed, not sure)
$ sudo pear config-set auto_discover 1
Install PHPUnit: (I think `sudo` is needed, not sure)
$ sudo pear install pear.phpunit.de/PHPUnit
(In the future, will I use: pear install phpunit/DbUnit and
phpunit/PHPUnit_Selenium ?)
Configure wordpress-tests:
Edit wordpress-tests/unittests-config.php
and specify path to the WordPress codebase and database credentials.
2. Create a test database and a test user
$ mysql -h localhost -u root -p # for example
CREATE USER wordpress_test@localhost IDENTIFIED BY 'wordpress_test';
CREATE DATABASE wordpress_test;
GRANT ALL ON wordpress_test.* TO wordpress_test@localhost;
FLUSH PRIVILEGES;
3.
Read
http://blog.doh.ms/2011/05/13/debugging-phpunit-tests-in-netbeans-with-xdebug/
4.
If you're using Netbeans, and debugging phpunit on a *remote machine*
(I do, I have my WordPress installation in a virtual machine),
then I think you need to:
Add a Run Configuration to project `debiki-wordpress-comments`
(File | Project Properties | Run Configuration)
You could name it "Remote_phpunit_debugging"
Click [Advanced]
Select (o) Do Not Open Web Browser
Map Server Path: /var/www/wordpress/ (for example)
to Project Path: /home/you/path/to/wp-content/parent/dir/