• Hi, not sure this is something to be concerned about but, having enabled debug mode I now get large numbers of errors stating Undefined Index SCRIPT_NAME in several files relating to CCTM.

    Some of those files are:

    loader.php, line 90
    SummarizePosts_Widget.php, line 23
    CCTM_Post_Widget.php, line 28
    CCTM.php, line 460

    I’m running WordPress under a local Google App Engine environment with php v5.4.3.

    The reason I’m not sure whether to be concerned or not is that when I turn off debug mode, things seem to be working fine, though I am yet to create any custom content types.

    Regards
    Andrew

    http://wordpress.org/extend/plugins/custom-content-type-manager/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor fireproofsocks

    (@fireproofsocks)

    That definitely sounds like an environment issue. Each OS publishes server variables differently, so it sounds like Google App Engine is not publishing the SCRIPT_NAME the same way that Linux or Windows is. That’s unfortunate: the only reason I need the SCRIPT_NAME and path info is because 1) WordPress doesn’t include path info in its configuration details that are standard in pretty much every single other CMS application I have ever seen and 2) its bloated event-driven architecture starts exploding if you don’t limit certain events by other criteria (namely by which file invoked the event — i.e. you *need* the path info to keep the architecture from falling apart). At the end of the day you try to fix band-aids that shouldn’t need to be there in the first place. It’s kind of maddening and in my mind, it forever condemns WordPress to a juvenile hobby-horse system unworthy of production level sites. You uncorked a rant that’s been brewing for a long time, but it really blows my mind that a system lacking such basic and critically important features is as wildly popular as it is.

    Anyhow, re the matter at hand: I can’t troubleshoot this without access to a Google App Engine environment — I don’t know if there’s some other way that I can get the path info I need in the scripts.

    Thread Starter trotskyicepick

    (@trotskyicepick)

    Hi Fireproofsocks. That’s pretty much as I guessed. WordPress looks ideal from the point of view of my employer, but for me it feels to simplistic.

    I have mental health issues (and thats the last I’ll mention it), but I’ve always enjoyed working with more complex environments, which WP isn’t. Example….I’d like to use Typo3 or ModX Revo, but I’m now tied to Drupal (complex, but no real backend management), and WordPress.

    Anyways, given my comment that no errors are shown until debugging is enabled, means CCTM will most likely work fine. Your and others work in developing plugins is much appreciated, don’t forget that even if you are dissillusioned with WP.

    (as an aside, the reason for using CCTM was for making WP more like a “proper” CMS, I’m using other plugins to this end also. WP is user friendly so I’m afraid it’s always going to be there.

    Plugin Contributor fireproofsocks

    (@fireproofsocks)

    I dunno… I don’t trust scripts/apps that throw warnings or notices…

    If you can grant me temporary access to the Google instance, I’d be happy to take a look around and see if I can’t make the CCTM compatible with Google’s servers. There’s got to be something on there that discloses path info…

    Thread Starter trotskyicepick

    (@trotskyicepick)

    Unfortunately granting access won’t be possible as it’s local to my laptop.

    Given the popularity of CCTM and the fact I wouldn’t have even realised there were errors if I hadn’t enabled debugging (out of curiosity if I’m honest), I’ll continue as normal and create some content types.

    If I come across any genuine issues I’ll let you know.

    In the meantime, I’ll try and get some answers off Google, if anything of use comes of that then again I’ll post to let you know.

    Thanks for your responses.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Undefined Index SCRIPT_NAME’ is closed to new replies.