Hi @Marcus,

I cannot get the Wordpress Connector module to import at all. and am not getting any error messages so I'm quite frustrated.

I have installed:

1. SilverStripe Blog module (v0.4.1)
2. External Content module (v0.2.4)
3. Wordpress Connector module (v0.1) (folder is named wordpressconnector as instructed)
4. A fresh install of Wordpress v3.1.2 with the content I want imported in its database

I have rebuilt the SS database with no errors. Everything looks good in the CMS.

Now, I can’t seem to find any detailed instructions on how to go about doing the actual import, and it seems fairly self-explanatory so on the External Content tab I:

1. Created new WordpressPostContentSource (I only need the Posts)
2. In my WordpressPostContentSource, I have the following settings:
a. Wordpress Base URL: http://www.clickfox.com/blog/
b. Wordpress Blog ID: 0 (verified as correct)
c. Working credentials
e. Blog to import into: Blog (verified exists in CMS)

When I click on the “Start Importing” button, I get the green ajax message “Starting import to Blog...” at the bottom of the screen—for a few seconds—but then nothing ever happens after that and I don’t get any errors and nothing is imported. What am I missing?

Thanks in advance,
Garrett

In the External Content section of the site, once you create the wordpress connector, do you get the tree view of the wordpress content? Can you check your webserver error log to see if there's anything being output there?

I've sent a link to Andrew Short who wrote the wordpress connector who might have some more ideas.

No, I don't see *anything*. Which Log, the remote server of my local SS?

//Garrett

Marcus, when i click the "Start Importing" button, I get java errors. Chrome is giving an error of "Refused to set unsafe header "Connection". Other than that, it appears the button does nothing, and doesn't give any messages. Any ideas?
Thanks

Do you have the queuedjobs module installed as well? If so, check the 'Jobs' section, as it's possible the job has been created but is not executing yet.

If you don't have the queuedjobs module, it's possible that the import is running, but it's taking quite a while and tying up the connection. First try doing the import on a small set of content (maybe just a single page to begin with). If that works out, then you should probably use the queuedjobs module to be able to do the background processing of the import.