Civivolunteer not responding

[robinhood]

I am trying out Civivolunteer on a test site running WP 3.7.1.  It installs ok, but on the Volunteers tab of an event, the "Define volunteer needs" and "Assign volunteers" buttons don't do anything.  Backtracing is on, but there are no errors or warnings, nothing in the logs.  The "Log volunteer hours" button works and I can record hours against volunteer names as expected.  Any ideas on how to debug this?
Thanks.

[Flaf]

I faced the same problem yesterday.
The problem was the ressource URL for extension.
In my case it was a typo.

To confirm you can look at the java console in you browser, after trying to run the "define" or "assing" fonction.
Or you can look at the apache error log; you will see a "file not found" error.

Ether way the solution is to fill out the ressource URL.
And remember that it should be a URL not a file path (http://yoursite.com/wp-content/plugins/files/your_custom_dir/  NOT http://yoursite.com//var/www/html/wp-content/plugins/files/your_custom_dir/ . That was the cause of my problem.

[Coleman Watts]

FYI: Placing extensions in wordpress/vendor/civicrm is the foolproof way to do it - doesn't require you to set the extension directory or resource urls.

[robinhood]

That was it.  Thanks!

[edewsberry]

I'm having the exact same problem.

I have set my resource and directory url for extensions to:
wp-content/plugins/files/civicrm/custom_ext

I didn't understand the answer about NOT setting the resource and directory URL but putting extensions in wordpress/vendor instead ... can you explain that fix a little further to me?

Thanks.

[Coleman Watts]

The vendor trick doesn't work in WP, scratch that. 

I think your directory is right but remember that the url needs to be a real url (starting with http://) that will lead to that directory.

[Flaf]

I have set my resource and directory url for extensions to:
wp-content/plugins/files/civicrm/custom_ext

Sorry but you got that wrong on 2 count:

1 - The ressource directory should be an absolute path and it must end with a "/"
/var/www/html/wp-content/plugins/files/custom_ex/

note: the "/var/www/html/" part may be different on your server but it is very unlikely to be "/wp-content" as the root.
 
2 - The url must start with "http://...." or https://..." and it must end with a "/"
http://YOURDOMAIN.ORG/wp-content/plugins/files/custom_ex/