Profile cover photo
Profile photo
Textpattern CMS
A flexible, elegant and easy-to-use CMS
A flexible, elegant and easy-to-use CMS

Communities and Collections

Calling all jQuery gurus. I think I'm just not being clever enough here. I have a form I want to submit. Inside that form are a bunch of <input>, <select>, etc controls that can be turned on and off (show() / hide()) by changing the state of other elements.

So after the user has finished selecting stuff and typing, they're left with a bunch of form fields they can see, and some that are invisible, depending on what they've chosen. There are also some important <input> elements that are of type="hidden" which I have already put in the form: IDs, stuff like that.

When they hit submit, everything is sent to the server, whether it's visible or not. What I want to do is trap the submit button (easy) and remove any element that is NOT VISIBLE but leave alone any VISIBLE and type="hidden" elements, then submit the form. The result is that the server only sees my special hidden content, and any visible entries as a result of user interaction.

I was hoping there'd be a nice neat jQuery-esque way of doing this. I've tried things like:

jQuery('#my_form').find('input, select').filter(':visible').remove();


jQuery('#my_form').find('input, select').filter(':not(:hidden)').remove();

and a few other crazy combinations of selectors, all of which do get rid of the invisible elements, but always strip out type="hidden" as well. jQuery seems to treat those as 'invisible'.

Do I really have to go through .each() element in the form and check whether it and all of its parent elements are css('display') !== 'none' to determine if it's visible or not? Or is there a way to be cunning with selectors to leave hidden elements alone but remove invisible ones?

Thanks in advance for any pointers.

We need a big, beautiful profile image for our G+ Page. What should it be and who's going to create it?

One idea: An admin-side screenshot of out-of-box Write Panel using Hive.

Our logo is already used in the profile name avatar, so whatever image is used, it probably shouldn't be hammer-an-chiseled to death.

Post has attachment

After some reconsideration of how G+ Pages and Communities can work together, we're going to keep this Page up. It will serve as a Txp brand voice in the G+ Textpattern Community, and perhaps other communities too, like if we want to go crash the WordPress community or whatever. ;)

So, what's cookin'?
Add a comment...

Post has attachment

Textpattern is excited to announce it's new G+ Community... 

We are moving all operations over there and closing down this Page, as well the Textpattern LinkedIn Group, which has never been very active. The new community tool provides for much better interaction and organization of topics, which should make a lot of difference in terms of exchange and relevancy. Please head over there and become a member.

We thank you!

Add a comment...

Post has attachment content assessment

If you haven't seen this about facilitating the work towards rebuilding the Textpattern website (etc) — BEGINNING WITH THE CONTENT — have a look.
Add a comment...

Post has attachment
Textpattern LinkedIn Experiment

We're trying a little experiment over at the Textpattern LinkedIn group. Since the whole point of LinkedIn is about job networking (true), and since there was really no focus for our LinkedIn group before (nor much life there as a result). We're orienting the focus of the group around client–provider connections. I (Destry) even ran a little poll a while back and it was near unanimous that we try doing it (one person voted for the option: "Do nothing. I like comatose groups." Ha!).

To provide a sense of order to things, a subgroup was created under the existing parent group: Textpattern CMS Service Providers. Anyone can join this group—and you have to if you want to see the posts within it, which is normal LinkedIn procedure—but only Textpattern "Providers" can post in the subgroup, and even then can only make ONE post to announce themselves. Once you join the group, whether you're looking for help or providing it, read the Group Rules! They make it more clear.

Discussion about this experiment is taking place in the parent group, which has been renamed from Textpattern Professionals to Textpattern User Community, which should be a lot more inviting now to people who are not strictly professionals. That's important for this client–provider thing to work.

We realize LinkedIn isn't everyone's cup of tea, but nothing is. Some like it left, others right. Some up, others down. Black/white. In/out. Whatever.  It's simple. If you don't want to take part. Don't. But don't knock either.

So, whether you're looking for help or legally providing it, go join the group and let's kick the tires around. Let's see if we can make the LinkedIn group work for everyone better in a business way.
Add a comment...


Textpattern has made ONE category, so your votes are essential to  represent. Category competition is:

- CMS Made Simple
- Concrete5
- ProcessWire
- Liferay.

Not the usual competition, so it should be very interesting.

Voting closes 12 November, so get over their now and do it!
Add a comment...

Post has attachment
NOMINATE Textpattern in the Critics Choice CMS Awards

If you haven't done this yet, DO IT NOW! Today is the last day.

Then get your buns back there on time to VOTE for Textpattern too!

Don't forget.
Add a comment...

Post has attachment
SUBJECT: Textpattern professionals in LinkedIn


Some of you may be members of the Textpattern LinkedIn group (, or maybe you didn't even know there was one. Either way, this message is for you.

There was a poll recently posted there about how to best use the group. Here is the poll and associated discussion...

You should cast your vote. Otherwise, as these "vote" things go, you get what you don't speak up for.

Below is a proposal with regard to one idea reflected in the poll: to proactively use the group for Textpattern client/provider networking. Considering the nature of LinkedIn, this seems like the appropriate reason for which to shape this group. 

Other Textpattern channels provide distinct purposes that the LinkedIn group doesn't need to compete with. If people want to pose questions to the Textpattern dev team directly, they can use Twitter (@textpattern). If they just have general user questions about Textpattern, they can go to the Textpattern Support Forum ( If they need friends, they can go to the Textpattern Facebook group. And so forth. But in LinkedIn, the group is practically zero-active. In fact, the most activity it sees is deleting spam accounts, and that's not an activity worth maintaining.


This isn't a complete plan for the entire LinkedIn group, but I think it will give the group a big jolt, and if you provide Textpattern services, you probably don't want to miss out on it.

First, I (or one of the other managers) would create a subgroup called "PROVIDERS" (unless someone has a better one-word idea for a name; but remember the main group is already titled "Textpattern Professionals", which anybody has to be a member of first). This subgroup is intended for use by people who have business licenses and provide Textpattern services.

Each person (or agency) that is a provider can make one entry in the PROVIDERS subgroup to "advertise" their status/availability as a Textpattern service provider. It can be whatever you want to say; from a simple link for your business site, to full use of the post's character limit.

Ground rules to be respected (and policed by the community, and enforced by the group managers):

1) Providers should offer services in development, design (e.g., themes), content, information architecture, or all the above. (Web hosting should be a different subgroup, if anybody wants it.) 

2) Providers can make ONE entry. The sooner made, the higher up on the list they are, since we can't control it any other way. (Thus, it's to your advantage to get your entry in sooner than later.)

3) The PROVIDERS subgroup is not a discussion thread, so anybody, provider or otherwise, who makes a general comment in that thread, their comment(s) will be deleted. Repeat offenders will be banned from group. (These rules will be made clear in the top-level Group Rules.)

4) Verifications of a provider's status as a Textpattern service provider will be made to the best of abilities. If we go to your site and it doesn't represent a licensed business in any way, or you don't have any proof of using Textpattern, or you don't even have a website, then this subgroup isn't the place for you. All group members will contribute to policing this.

5) We will assume that any use of "Like" on a provider's entry (regardless of where they come from) will mean a vote of confidence of that provider's ability as a Textpattern service provider for the services they advertise. Ideally these would come from past (or current) clients. However, a provider can even like their own entry (since LinkedIn allows it), so we'll also assume that real likes for a given provider begin at counts greater than "1". Essentially n-1, where "n" is the number of likes shown when greater than none at all. Note that it's easy to verify likes; account names are associated to the likes, and if a client writes a LinkedIn referral for the provider, then it's even more obvious and legitimate if someone investigates.

In addition, we would make the top level "Textpattern Professionals" group an open group so it's easier for potential "clients" to find providers. We may need more group managers to help with zapping the spam in that case. Volunteers welcome.

We would also put a custom logo on the PROVIDERS subgroup to help bring attention to it. (Anyone up for making that graphic contribution?)

That's about it. 

I don't think it's necessary to create a "SEEKER" subgroup. I think we should think of the Textpattern Professionals group like a yellow pages of Textpattern pros, where people needing services come and pick somebody based on what they find. Thus, it's to each provider's benefit to use their PROVIDER entry to the fullest.

We can, however, create subgroups for other Textpattern topics, like "SHOW YOUR SITE", or whatever, and you can imagine that showing client sites would also be to a provider's advantage in marketing themselves, while at the same time offering a topic for convivial discussion in the group.

If you have any questions, suggestions, or concerns about this, now is the time to speak up, and you should really do so in the LinkedIn group before we create the provider subgroup, which we'll do by 15 October.

This message was posted here because LinkedIn doesn't allow a message this long. 

Thanks for your attention! 

+Destry Wion,
A Textpattern service provider in content strategy, architecture, and design.
Add a comment...

Post has attachment

They are important in technology too!

This article was brought to our attention by Els Lepelaars. From the article...

"I agree with our West Coast Editor, Drew Olanoff, on just about everything – [but] his insistence on writing ‘foursquare’ is the one thing I just can’t get on board with. Drew used to work in tech PR and knows the frustrations caused by journalists writing company names incorrectly. I understand – the first time I covered SoundCloud, their PR rep emailed me to politely ask me to cap the ‘C’ (I’d written ‘Soundcloud’) – that’s fine, but an entirely lower-case name in news reporting is insane."

Thankfully we're not "textpattern", and we've even been using #Textpattern hashtags when most people don't bother with the capital. But one thing for sure, we are not "TextPattern", and that's why we've got to make things clear—so the journalists and product reviewers don't keep getting it wrong and spreading the erroneous identity.

The article is relevant and harks back to why the magazine's editorial team has been taking hard looks at Textpattern's own brand (

Beginning Textpattern 4.5 +Philipp Schilling's new logo will be in +Phil Wareham's core themes, and later the new branding work will reflect in the family of sites. Logo files will be made available for other project use, but so will brand use guidelines along with the existing editorial guidelines. The slickest way to make all this information available in one centralised place, would be to establish a professional-looking mini-site for the purpose, similar to what Ubuntu has done (, and probably as a subdirectory in one of the existing family sites; would be a reasonable call. Drafts for the copy of such information have been started, and the newest member of the editorial team, +Lawrence Ladomery will be helping on the audience definitions, and so forth. Deciding upon a home and making it pretty for public use will come later.
Add a comment...
Wait while more posts are being loaded