any idea????

THANKS.

Yan. P

Is it possible for to create custom post type entries with the import, rather than posts?

And can custom fields in EE be mapped to relevant custom fields in WordPress?

The best approach for any site that is big enough to have those concerns would be to parse the EE data into WP or other format using standalone PHP and MySQL scripts that circumvent the CMS’s entirely.

Your script should probably work, for standard ‘blog-like’ set-ups, but that person mentioning the 15 different weblogs, which probably have 15 different field groups, potentially related data, and more, that’s going to need a lot more work on both ends, unless all 15 weblogs/channels are formatted exactly the same. Which I’ve seen done, but isn’t usual.

While the import process MAY BE the same, I highly recommend AJW Export http://devot-ee.com/add-ons/ajw-export to get data out of EE (free add-on). There’s other add-ons, notably Export-It ($65), but AJW Export works super well, if you can identify the fields you want. Additionally, I just use Sequel Pro (a MySQL GUI) to do query exports to SQL, CSV, or XML.

If your data is simple (title, date, author, summary, post) and you want WordPress, then the script should work without too many hiccups. But otherwise, both modifications to EE data and or WordPress structure will be required.

I just wanted to correct, some errors about ExpressionEngine mentioned in the article. The author mentioned he was unfamiliar with EE, so it’s easy to make these. I’ll started with the full list:

»»Licensing Fees for use: $99 – $299««

It is what it is, but it’s really only expensive when compared to free, not when compared to high-end CMS that can cost upwards of $10,000, and EE can provide lots of the same functionality and is easier to use and modify, with its open architecture.

»Multiple websites from same CMS? Add another $80 – $200««

Actually, you can add additional websites for free or for cost. EE provides both methods. The free method is frequently referred to as the old school subdomain, multi-domain method. Access to all content is shared in the backend, but you can have as many or few sites as you like or need at no additional cost. We use this method for most of our nonprofit clients. It works well.

The preferred method, for many, is using the Multi-Site Manager (MSM). That’s what the charge of $199 (which gives you 3 sites, and you can add more is for). What MSM does is separate content. When logged into X site, you only see entries for X, templates for X, field_groups for X, etc. This appeals to a number of people, especially if the sites are widely disparate. There are other benefits with MSM as well, but I won’t go into

»Add-ons: Expensive. Average cost for EE add on is $40.««

I’d say less than that, since there are a number of free and open source accessories, extensions, field_types, and plug-ins; but modules are generally paid for an can run as low a $5 or as high as a $300 (possibly more). I always compare the cost to the how long it would take us (Nonprofit Tech) to develop it for the client and my perception of the skill of the developer. Generally, its far cheaper to grab a pre-built module, which has more functionality than we currently need, then to spend more than 2hrs building it ourselves.

»»Usability: Unable to navigate easily between posts. System requires that you navigate back to entire list of posts.««

This one is definitely a lack of experience. You can easily set-up navigation between entries with ExpressionEngine. It has previous and next tags available for use. Or if you prefer you can set-up recent post, popular post, recommended post, favorited post, most mailed or shared posts or a number of other methods you wish to come up with.

»»User Management: Unable to assign fine tuned settings to users.««

User management far exceeds WordPress out of the box, but I’ve never used the Capability Manager, but since it hasn’t been updated in almost 3 years now, probably never will. Though there are other plugins. But that is also true for ExpressionEngine. There is a breadth of Membership/User Management add-ons depending on what’s important to you—managing subscriptions, paid membership, providing more detailed posting and access privileges, etc.

»»Documentation: Even the documentation written by EE doesn’t work properly (more recent specific example; exporting EE entries into a txt file. FAIL).««

Can’t really disagree with this one. While, I can say, ExpressionEngine docs are good, especially if you come from the world of open source, where documentation sucks so hard. I can also say, their by the number methods, doesn’t do much for helping a new person really learn ExpressionEngine or guiding them through the process of building a site.

I’ve been using ExpressionEngine from when it use to be pMachine, and even I can say, some times I read the documentation. Pause, go back and read it again, then say, ‘WTF?’ and search the forums, StackExchange or Google for a better response. Their User Guide is like an instructional manual, that primarily focuses on giving you definitions for all that new terminology. There are examples, and those are useful, if you’re already speaking the same language. If not, well, it’s like you’re speaking two different languages, with just enough common words to cause chaos.