theWebalyst

Microbe,

Thanks for your comment, but I think it is unfair and untrue as I’ll explain.

You say this doesn’t help “in any way” to comply with the EU privacy directive. What is needed for compliance depends on your website, and for most websites the EU Cookies Plugin will be all that is needed for compliance. Certainly some will need to do more, but most will not.

As explained in the documentation, the solution provided by the EU Cookies Plugin will be sufficient for almost all websites, and mimics the the compliance measures taken by the website of the UK government department that oversees implementation of EU privacy policy, the Department of Culture Media and Sport. The enforcement body is the ICO, and this is overseen by the DCMS, so I think it is fair to follow the lead set by the DCMS which uses Google Analytics.

You only need to do more than this if your website uses cookies in ways that are intended to be caught by the stricter provisions for consent, such as cookies used to track individuals across websites (typically when serving adverts). If your website does this, you certainly do need to do more, but as I pointed out this plugin is aimed to provide a quick solution for the majority of websites which just use Google analytics and it achieves this.

The important point is that everyone needs to do something! So getting informed is important, and I ask people to check after installing to ensure what the plugin generated privacy page says about their website is in fact true.

If you maintain your position I’d appreciate you being more specific about why you think the plugin will not help comply with the directive.

Mark

Mark, Thanks for following up my question. I’ve made a note to try your solution when I resume work on this plugin. Being able to move stuff out of the theme and into the plugin is very helpful.

Thanks!

Mark
[sig moderated as per the Forum Rules]

Using WP3.1RC-1 I’ve found custom post types to be far more limited in application than they need be.

For example, there is as far as I can see no way to change the way a custom post type is treated from ‘like a post’ to ‘like a page’ unless you edit the theme. But since plugins are how you build new apps with this powerful new feature, it is severely limiting their usefulness and ease of application, if every such plugin has to have the website’s theme tailored for it to work effectively.

An example customisation would be for is_page() to be something that can be altered for a custom post type.

Ideally WP would have a set of behaviours defined, each aligned to the standard types (post, page, archive etc.) and for the custom post type to be able to say: “treat me as if I am /like/ type y”. So themes render me as if I am y, even though I am type x, and no theme has ever head of type x.

A natural extension of this will be the ability to define custom behaviours (perhaps a better term would be “display pattern”?), in which case a theme can be written to do something particularly bespoke for this new kind of data object.

Mark
P.S. In the mean time, if anyone knows how to make a custom post type appear to a theme as if it were a page rather than a post PLEASE let me know! Its a major handicap to plugin writers until this can be done.

Ahah! Sorted, thanks guys. So much to learn here ?? and so much undocumented.

Would be good if the has_archive line was in the sample in the Custom Post Types docs (https://codex.www.ads-software.com/Custom_Post_Types) so I shall put this forward.

Thanks Andrew but it still does not find https://thewebalyst.com/products/

I now have the following (is this what you meant?)

function create_post_type() {
  register_post_type( 'twec_product',
    array(
      'labels' => array(
        'name' => __( 'Products' ),
        'singular_name' => __( 'Product' )
      ),
      'public' => true,
      'has_archive' => true,
      'rewrite' => array('slug' => 'products')
    )
  );
}

The usability for content editing on WordPress is very poor. Not surprising for a blogging platform, but my interest is in websites where blogging is an option, so CMS is primary and I’m coming from that direction.

WordPress needs an in depth review of usability for content management. But to be honest, even very basic things are in my opinion dismal. I don’t have time to put together a list right now, but getting to pages for editing, and the editing UI itself is terrible.

There isn’t undo. The allocation of screen real estate makes editing a page feel like I’m using an iPhone. Scrolling doesn’t work (page up/down frequently scrolls the page instead of the edit window). Accessing pages on even a small site is horrendously longwinded (again exacerbated by poor use of screen real estate – i.e. not showing many pages in the page list). These are just a few things that spring to mind, and are very basic.

I am committed to WordPress. Its a great platform and I will work with you guys when I have time to compile a more constructive review and suggestions for usability improvements, but right now don’t have the time.

The purpose of this post is to highlight this weakest of all aspects of WordPress. It is where other systems will gain an advantage if it is not addressed rapidly enough so I hope I’m not alone in identifying the issue, and that there are folks who understand usability a lot better than seems to have been the case so far. Its normal.

Usability is generally very poorly understood and implemented. So this does also present an opportunity for WordPress. This system has many killer features in other areas. Get it to the leading edge on usability and it will be untouchable!

With WordPress love,

Mark (in London)