Open GoogleCodeExporter opened 8 years ago
Excellent. It looks like you've found a defect that doesn't happen on any of
our developer's workstations. We need you to run BP-Media's built-in self tests
to help find the problem.
1) Create a database on your SQL server called "bpm_test". This database will
be *destroyed* during the testing process.
2) Create a user on the "bpm_test" database called "test" with password "test"
and give them root access to the database.
3) Open up a linux terminal window, or, if your web host doesn't have this
capability, contact their support department and have them do it for you.
4) In the terminal window, navigate to the
"/wordpress/wp-content/plugins/bp_media/unit-test/" folder.
5) Type "php test.php" and press enter
6) Copy the output displayed in the terminal window, and paste it into this
ticket.
Thanks!
^F^
Original comment by CarlRoett@gmail.com
on 29 Dec 2011 at 6:26
Hi,
So here is what happened. I tried to create the database and the username as
requested but since my webhost is a shared hosting, it puts my username before
the database name and the user of the database.
Anyhow I asked my webhosts to run the php script and this is what they got:
: # php test.php
: RUNNING TESTS FROM: /home/cabonkco/public_html/wp-content/plugins/bp-media/
: Loading PHPUnit Portable... OK - Version: '3.5.13'
: Warning:
require_once(/home/cabonkco/public_html/wp-content/plugins/bp-media/unit-test./b
pm-testlib/bpm-base-class.php): failed to open stream: No such file or
directory in
/home/cabonkco/public_html/wp-content/plugins/bp-media/unit-test/test.php on
line 112
: Fatal error: require_once(): Failed opening required
'/home/cabonkco/public_html/wp-content/plugins/bp-media/unit-test./bpm-testlib/b
pm-base-class.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in
/home/cabonkco/public_html/wp-content/plugins/bp-media/unit-test/test.php on
line 112
: =========================================
Any suggestions?
regards,
Akul.
Original comment by coola...@gmail.com
on 30 Dec 2011 at 1:37
You have the first server we've ever found that can't run our debug tools.
We're updating our code to work around the error, and we'll get back to you in
a few hours.
Original comment by CarlRoett@gmail.com
on 30 Dec 2011 at 1:57
Thanks :) I really like the plugin though. It would be great if it works. Do
you know if I can get exif data to display using the already released version
of the plugin BP Album?
Original comment by coola...@gmail.com
on 30 Dec 2011 at 2:34
I am having exactly the same issue.
Any help yet?
Original comment by nils8...@gmail.com
on 18 Jan 2012 at 10:32
We have a new nightly build ready for testing on Windows platforms.
We haven't finished debugging it on UNIX family platforms yet. We put a huge
amount of developer time (120 hours) into getting this nailed, and now have
some solid debugging tools.
Expect a nightly build up in the next few days.
^C^
Original comment by CarlRoett@gmail.com
on 18 Jan 2012 at 10:41
[deleted comment]
[deleted comment]
[deleted comment]
I am having exactly the same issue. how I can correct it? I've 1.5 budypress
version
Original comment by ADi...@gmail.com
on 24 Apr 2012 at 7:20
Please copy the error information from your web server log file and attach it
to this ticket.
We'd *really* like to find out what's causing this defect and fix it, but we
can't replicate it on any of our team member's workstations.
^C^
Original comment by CarlRoett@gmail.com
on 25 Apr 2012 at 4:23
Original comment by CarlRoett@gmail.com
on 25 Apr 2012 at 4:23
Getting the same issue on my development box. I am using MAMP Pro v 2.0.5, PHP
5.3.6 (also tested PHP 5.2.17) running on OS X 10.6.8
Standard WP 3.3.2 (Akismet & Hello Dolly)
BuddyPress 1.5.5
Original comment by sheas...@gmail.com
on 3 May 2012 at 6:52
UPDATE
Increased memory allocation in .htaccess and issue is resolved for me:
php_value memory_limit 256M
The minimum amount is 35M for it to work, anything less causes the 500 Internal
Server Error
Hope this helps.
Stephen
Original comment by sheas...@gmail.com
on 3 May 2012 at 6:55
Original issue reported on code.google.com by
coola...@gmail.com
on 28 Dec 2011 at 8:57