bamajr

I would also like to add, that the control of comments on pages is not working. I have comments turned off on every page, but IntenseDebate doesn’t acknowledge those settings, and displays the comment section anyway.

When I disable the IntenseDebate plugin, all my pages show that comments are enabled, even though they were not enabled before nor during the time IntenseDebate was installed.

Yes, I’m very familiar with hacking the theme and/or plugin files to remove the offending content. I’m just sick of having to do it over and over again, every time the theme or plugin is updated.

Psychic huh? Well, let me know what you find out ??

FYI:

If one were to use the Codepress Admin Columns plugin (https://www.ads-software.com/extend/plugins/codepress-admin-columns/), one can enable/disable columns, and specify column width (by percentage).

However, A WORD OF CAUTION: The Codepress Admin Columns plugin has a little glitch in that it has to be set to default settings before modifying plugins, which may have been installed/activated/deactivated after the Codepress Admin Columns plugin was installed and configured. Otherwise, it may do WEIRD things to your column order and widths.

This glitch is not seen all the time, and I have not been able to single out any specific plugins that may be causing the problem. I do know that I experienced it with the Reveal IDs plugin, but can’t yet prove which plugin caused the issue.

Yoast…

This is s pretty huge deal, even on a cinema screen monitor. Initially, I thought the WordPress SEO columns were fantastic, but all the added columns really clutter the All POSTS/PAGES area. This is especially true if a person already has other plugins adding columns to these areas.

For instance…

I have the “Reveal IDs” plugin (https://www.ads-software.com/extend/plugins/reveal-ids-for-wp-admin-25/) enabled, to show the IDs of all POSTS/PAGES and etc. This plugin added 1 column, with the numerical ID only.

Your plugin added 4 columns.

When I view All POSTS in full screen mode, on a 23 inch Apple Cinema Display, the “Title” and “Author” columns have already started bunching. So those with a smaller monitor and/or not viewing the page in full-screen, are simply presented with a garbled mess, in the “Title” column.

I suggest only adding the visual “Color” icon column and dropping all other columns. I would drop the remaining 3 columns in both All POSTS and All PAGES.

Your plugin is (and has been) very solid. You have done a fantastic job with its development and the support after release.

For visual people, like myself however, three of the additional columns added (), in the latest plugin version, are visually distracting and un-needed.

I’m curious if this issue has been resolved between the latest version of WordPress (3.3.2) and the latest version of IntenseDebate (2.9.4)?

If it helps, I’ve tested this resolution/method on a couple independent systems and it works fine.

you don’t have to delete the existing JetPack directory. You could just delete the contents within the JetPack directory. Then FTP the contents of the JetPack plugin from your computer to the server.

That is a great option, but it shouldn’t be necessary. I don’t have a problem with auto activation nor the adding of new modules. The problem I have is that it stomps on other plugins, without being remotely as functional or resourceful.

Can’t something be done about this so that JetPack isn’t stomping on a plugin with a significant history and contribution to WordPress?

Personally, I’m more apt to use something from the same people who develop WordPress, but the contact form, built into JetPack is so significantly crippled, I don’t see why the developers wouldn’t have created a way for the two to co-exist.

I would suggest that Automattic/WordPress bring in the Contact Form 7 team, to fix the JetPack Contact Form, taking on more of the features of Contact Form 7.

As it sits now, Contact Form 7 isn’t just far superior to the JetPack Contact Form option, it makes the JetPack Conctact Form development attempt look amateur.

It looks like you’ve found out about the over riding of one to the other. Does this have to do with the shortcodes used between the JetPack Form and Contact Form 7?

Can you provide a link to an example of what you are seeing?

Also, can you provide for us, the plugins and theme you are using?

Ok… The default parameter is a TERRIBLE option!

[contact-form subject="Bamajr.com Contact Form" to="[email protected]"] [contact-field label="First Name" type="name" required="true" default="First Name" /] [contact-field label="Last Name" type="name" required="true" default="First Name" /] [contact-field label="Email" type="email" required="true" default="[email protected]" /] [contact-field label="Website" type="url" default="https://www.domain.tld" /] [contact-field label="Message" type="textarea" /] [/contact-form]

If you use the default parameter like I have shown, the form passes validation and can be sent, without any one actually typing anything into the form.

There needs to be something like the HTML5 placeholder=” ” parameter.

Oh, and now that the validation can of worms is open… this really needs some customizable validation controls. Blindly accepting form submissions that pass Akismet is a TERRIBLE idea.

Also, if the profile accepts username, first name, last name and nickname, they should each match up to a “Field Type” within the JetPack form.

@ Tim Moore:

Let me explain the issue a little further.

My username is “Bamajr” and if I’m logged in, both fields used for FIRST NAME and LAST NAME are populated with Bamajr.

This is a NAME field, not a username field. So, if a person is logged in why is either field being populated with the username and not FIRST/LAST NAME?

I think the default parameter may help, but I haven’t tried it yet. I’ll let you know when I do.

I’m not sure this will help any/all of you who are having issues with the contact feature, but I would take a look at any plugins which modify or allow modification of shortcodes.

I can’t remember the name of the plugin I tried before, but there was an issue in how it used/implemented its various shortcodes.

Also, I’m highly skeptical of any WordPress installation using “Register Plus” or “Register Plus Redux” plugins, with all the problems which have been verified with them.