Consolidating the three WordPress comment files?

  • WordPress has three comment files,
    – wp-comments.php
    – wp-comments-popup.php
    – wp-comments-reply.php that each do similar things and then do an HTTP post to wp-comments-post.php that in turn does some checking of its own and then inserts the comment into the comment table. Are there are plans to consolidate the three “front-end” files into one for easier maintenance? If nothing else the “Form” section could be made into a common function.

Viewing 6 replies - 16 through 21 (of 21 total)

  • Well I decided to go with a couple of Kitten’s plugins (assuming everyone was breathlessly awaiting to hear what I decided to do) and so far so good.

    You can’t equate the misuse of pop-ups by internet sites to web standards. Standards of conduct are not the same as standardization of tools and processes.

    Then why is the target attribute no longer present in the HTML 4.01 Strict and XHTML 1.0 Strict specifications? These specifications are the standards that show us the way forward in markup for the modern web.

    See also #2 on Jakob Nielsen’s Top 10 New Mistakes of Web Design from 1999, and Day 16 ‘Not opening new windows’ from Dive Into Accessibility.

    Let me stress that I’m not trying to pick a fight here. I just want to clear up this issue with some healthy discussion… Peace.

    (And maybe the moderator can email me to explain what was wrong with the last part of my previous reaction…)

    Popups
    I lot of people like their popups.
    I’m sure they could be dumped out with no issue, and I know for a fact that the forum here would then be flooded by requests for them to be put back.

    Xhtml Strict – WP does not validate as that out of the box, with or without popups.

    It’s a single file, it can be deleted, I just can’t see why removing it achieves anything except hassle for those WP users that elect to use it. We constantly have people saying stuff like “Make asides an integral part of WP”or “WP should have meta tags” or some other code that would be used by the minority yet would reside in the core – effectively code bloat. This issue would save what on the zipped download ? 1K ?

    It is within standards, it provides user choice, it does not impede non-popup owners.

    Live and let live ??

    Just saw your references:
    Yes, we do know of those standards and texts, but my pov is this – it’s not my blog.

    I can advise, I can point out pros and cons, I can help get it working, I can help geting it valid if the user wants but in the end, it’s not my site and I must respect the deicision of the site owner.
    We’ve ALL committed web sins with regard to every aspect of site stuff, so why shouldn’t new people be allowed to do so too ?

    Getting OT:
    The web and in particular blogs, have been trumpeted as being there for individuals. But if everyone who wants a blog sees all this stuff about functionality, standards, rights and wrongs of how to code etc etc .. hardly conducive is it ?

    We all have our little spaces, and just like I would’nt go into someone’s house / shed / wherever and criticise aspects, I won’t tell someone how they should or should not run their site.

    I hate leopard-print, doesn’t mean it should be banned though – someone likes it.

    Sure I’ll let live. As I said before, I don’t have a personal issue with it. But as the topic starter implied, it would ease development, if not for the core WP developers, then at least for customizers and theme devs. Anyway…

    And by the way, WP can very easily be adapted to a Strict doctype, it’s really not that hard. I use XHTML 1.1 (my blog) and HTML 4.01 Strict (client) on various WP driven sites.

    I use pop up comments on my photoblog because that is a single post site. I wanted a seamless move/navigation using the prev and next. Without my popup comment, this could have not been implemented the way I wanted – if a user wanted to look at comments, I was hosed without it.

    Leave my pop up comment alone! ;d Yes, there is a valid use for them.

Viewing 6 replies - 16 through 21 (of 21 total)
  • The topic ‘Consolidating the three WordPress comment files?’ is closed to new replies.