in reply to Re^2: Message Outbox: "delete" msg box button? (dev cycle?)
in thread Message Outbox: "delete" msg box button? (updated)

Yes, at least until we get a separate testing instance back up again (which I foresee only after a move to git or whatever). Testing in production isn't that bad here IMO, as the risks are low and usually people stick around until they're convinced that their change actually works :)

  • Comment on Re^3: Message Outbox: "delete" msg box button? (dev cycle?)

Replies are listed 'Best First'.
Re^4: Message Outbox: "delete" msg box button? (dev cycle?)
by LanX (Saint) on Jan 03, 2016 at 19:21 UTC
    OK thanks.

    some questions:

    1. Is it OK if I implement a JS solution here?

    2. Which CGI version does PM use?

    3. Is it possible to clone/fork a node for testing? (Of course overkill here, just in theory)

    Cheers Rolf
    (addicted to the Perl Programming Language and ☆☆☆☆ :)
    Je suis Charlie!

[reply]

      As long as the site still works without Javascript (which I assume for this form), Javascript is OK. I just don't like to encourage leaving Javascript switched on, as I think it's bad security practice.

      For CGI.pm , I'd have to look. I assume it's a 3.x version, likely patched locally.

      It's easy to copy a node, but that node stays around forever.

[reply]
        OK I created a patch, and by repairing typos¹ I accidentally created two (broken) duplicates.

        ( Sorry kind of learning by doing about the patch system =)

        So it seems every patch is a node of it's own?

        Would it make sense to be able to test those patch-nodes directly?

        Cheers Rolf
        (addicted to the Perl Programming Language and ☆☆☆☆ :)
        Je suis Charlie!

        ¹) one of my nodelet hacks automatically inserts html-tags on submit ..

[reply]

In Section Perl Monks Discussion