• URL to the FORM: N/A
• The browser used: Firefox 3, IE 7
  
• cforms version: 9.3
• Your Wordpress version: 2.6.5

[desc]:

After installing and activating cforms, I can't find the panel to configure a form.

I found the thread -

http://www.deliciousdays.com/cforms-forum/troubleshooting/cforms-not-apearing-w-dashboard-tabs/page-2/

That conversation has gone on for 10 months over various cforms versions, I've tried some of the workarounds without success, and I hope you don't mind that I've started a fresh thread.

In particular, I tried putting an "echo test;" as the first line of
cforms_init()" [comment #29] and didn't see anything appear.

I also saw the note about abspath.php in the FAQ <http://www.deliciousdays.com/cforms-forum/troubleshooting/v9-upgrade-must-read-abspathphp-issue/page-1>. I tried recreating that manually, but it didn't help — and I now realize if things were working at all, I should have seen an error message.

The new information here is that this is related to the fact that I'm using the current WP feature to move the wp-content folder out from under the main WordPress directory. The structure I'd like to have is:

documentroot/wp-content/plugins
documentroot/wp-content/themes
documentroot/wp/ – WordPress core files.

I've tried setting the abspath to the /wp/ directory and making a symbolic link from wp/wp-content to the actual documentroot/wp-content/ directory, but that didn't help.

[I was logged in as admin, all other plugins were deactivated, I'm not on GoDaddy, etc.]

However, when I removed the WP_CONTENT_DIR and WP_CONTENT_URL definitions in wp-config.php and moved the wp-content directory back to it's "usual" location as a subdirectory of the main WordPress directory, Voila! the CFORMS II menu appears.

I tried wading through the various places the directory might have been defined/used, but I'm wondering if you've got suggestions here. [This is the second plugin I've bumped into with this problem -- 2 out of 6. I do understand that it can be hard to ferret out all the places that would be affected by a change like modifying a default directory structure.]

Thanks very much for what appears to be an excellent plugin.

Yes, there's a cforms_settings in the wp_options table. But that's with the setup that's working, so that's expected, right?

Give me a day or so to set up another system that shows the problem and I'll send you the (more interesting) link to that.

Thanks for your help with this!

Here's a workaround for the css problem:

$ cd wp

$ ln -s ../wp-content wp-content

It also seems to have resolved problems with the admin screen – turning on additional functionality.

[Sorry - 2 more questions here; both may be linked to the "nonstandard" directory setup.]

After checking my test system you said:

very odd wp 2.6.5 / register_activation_hook behaviour.

the reason is clear why cforms couldn't startup properly: register_activation_hook  never triggered the cforms init.

I suspect it's a 2.6.5 bug.

running the activation routine "manually" set all cforms settings and it works.

<!-- Start Of Script Generated By cforms v9.3 [Oliver Seidel | http://www.deliciousdays.com --><link rel="stylesheet" type="text/css" href="http://mysite/wp/wp-content/plugins/cforms/styling/cforms.css" /><script type="text/javascript" src="http://mysite/wp/wp-content/plugins/cforms/js/cforms.js"></script>

Creating the symbolic link:
$ ln -s  document_root/wp-content/plugins/cforms document_root/wp/wp-content/plugins/cforms

apparently fixes things.

Thanks!

I've run into enough other problems with other plugins that I've given up trying to have a "nontraditional" directory setup. If I get back to this, I'll let you know -- and if you want a test environment again, I can set that up.