zactoff

Could be that I’m not using it in a widget so didn’t even bother to have a look at it that way.

Just some code example like the above of how to use it would be cool. Not a biggie, it’s a sweet plugin.

As for CSS, I guess that depends on how far you want to go with supporting people who are new to the game (not counting myself in that, I just have regular “used to be a designer now I’m a developer” WordPress type issues).

Yeah, me too, cheers, documentation is somewhat lacking for this plugin, shame as it’s a good ‘un.

This is crucial… as this seems to be the only plugin that does what it’s supposed to.

Is there a patch on the way?

Apologies!

This is working after all, it was conflicting with some plugins that weren’t even activated.

Still could do with a bit more support from the authors though, or at least a caveat that it’s not supported closely.

The problem with meta-fields is that they don’t get included in the page revisions (one of my original points) thus rendering them useless where the client is updating content constantly with the need to revert if necessary.

I would argue that just because many people aren’t asking for this, it’s still desirable functionality in WordPress’ constant evolution from blogging platform to website CMS.

At the risk of continuing this thread needlessly, if this functionality was available in previous version of WP why would it get dropped? Just because not many people are asking for it doesn’t mean many people want it as people are by their nature, lazy.

Thanks, Ipstenu, this widget is OK in some of my installations but I’ve noticed with all the wysywig widgets out there that they can conflict and stop showing the text editing options when dropped in a widget. Ho-hum, onwards and upwards.

Nice one, thanks, still think this should be core functionality though…

Thanks for the link, had tried this on one of my sites and it hadn’t worked, tried it on another and it does so it must be conflicting with something. That’s why I was hoping it could be added to the core as I assumed there’d be less chance of conflicts if it was baked in.

I just wanted to register my request here in the hope that whoever the wordpress team are might take notice as this is something I keep coming up against.

Wasn’t looking for a fight :c)

I scanned your rant :c) but you can’t deny that WordPress started life as a blogging platform and has gradually become more a CMS like (for want of a better term).

The loop seems a more long winded way of accessing content compared to what I’ve seen of Drupal.

Your project looks interesting, but it’s too complicated for what I need, my clients often want to create a page where they can enter content that gets presented in various areas of the page/sidebar/footer etc., but they need to see it all together while editing rather than having a load of custom content types that they have to navigate between, or a load of dynamically assigned text widgets.

I was rather hoping that something like the multi-edit plugins could be developed properly and added to the core. You may not like them but they’re very popular and obviously fill a need.

Haha, I *really* don’t want to, but I know a lot of ex-WordPress developers who find Drupal a lot easier to use, not having to use ‘the loop’ being one reason among many.

Anyway, from a clients point of view, seeing this in the page editor is far less scary than maintaining a bunch of fields, especially if those fields aren’t wysiwyg.

This is one of those problems that keeps coming up, which is why I have de-lurked and raised it here.

Not entirely sure… perhaps the ability to add additional tabs when you’re editing a page that you could name and then call in the template, maybe using the_content(tabName); or something?

This has become an issue for me because where I’ve been using some plugins that sort of create this functionality (templ33t, page.ly multiedit etc.), apart from being usupported, they all seem to use meta-fields to store the data and these do not get included in the page revisions, there is also a big problem with them mangling content when flicking between visual/html view.

I use WordPress more and more to create CMS’ for clients this is highly desirable from their point of view – not having to think about hacking templates, however I’m not a hardcore programmer so may not realise the full implications of this request.

What I do know is that Drupal seems to support this functionality, but I really, really don’t want to have to learn Drupal having invested so much time learning (what little) I know of WordPress.

Ah, sorry, I was a little remiss in my explanation. The class I tried to add was called addToList, not EcampaignPHPList” so I don’t think it’s the quotes that are messing things up.

When I check the log (now I know where to find it!) there are several entries at the top as follows:

WordPress database error: [Table 'pen.wp_ecampaign_log' doesn't exist]
SELECT state, count(*) FROM wp_ecampaign_log GROUP BY state

WordPress database error: [Table 'pen.wp_ecampaign_log' doesn't exist]
SELECT checkbox1, count(*) FROM wp_ecampaign_log GROUP BY checkbox1

WordPress database error: [Table 'pen.wp_ecampaign_log' doesn't exist]
SELECT checkbox2, count(*) FROM wp_ecampaign_log GROUP BY checkbox2

WordPress database error: [Table 'pen.wp_ecampaign_log' doesn't exist]
SELECT postID, count(*) FROM wp_ecampaign_log GROUP BY postID

WordPress database error: [Table 'pen.wp_ecampaign_log' doesn't exist]
SELECT count(*) FROM wp_ecampaign_log WHERE 1=1

WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '-1' at line 1]
SELECT id, date, state, visitorName, visitorEmail, postID, checkbox1, checkbox2, info FROM wp_ecampaign_log WHERE 1=1 ORDER BY date LIMIT 20 OFFSET -1

I’m going to try and get you some money for this from the client (although it won’t be a lot). If you can provide the functionality we need it will help us enormously. You say the pestering is good but I’ll feel better about it if you’re actually getting something in return for the hassle.

Email me off list if you’d like to discuss, perhaps we can work together to iron out these wrinkles (I used to be in QA before jumping ship to pretend to be a web developer) zaccety (at) gmail (dot) com