This section is only for discussing issues pertaining to the PerlMonks web site itself.
For example, asking about how things work, or offering ideas on how the site could be made better.
I've just encountered an odd problem whereby the nodelets stopped part-way through. Looking at https://www.perlmonks.org/?node_id=11122359 the Nodelets only inlcuded the XP nodelet and the first half of the Approval Nodelet - it stopped just after the "moderation history" link. The rest of the nodelets were absent as was the page footer ("PerlMonks lovingly hand-crafted by Tim Vroom.", etc.). I had not been logged out, according to the rest of the page. To see if it was reproducible I opened the same page in a fresh tab and the nodelets all appeared as they usually do and the footer had returned.
Both requests would have probably been made at 13:27 BST (UTC +1) or so today.
I've never seen this before but it might, if related, shed more light on the intermittent 500s. HTH, either way.
Since past few days, I am not able to upvote any answers here at PerlMonks. I was able to upvote up until a few days ago, but it's been about 2 weeks, and I've checked at different times, upvote radio buttons do not show.
Many of the answers to the questions I asked were absolutely fantastic and the least I can do is upvote them. I've been referring to books and writing code, but the help offered here is far beyond imagination. It has been an eye opener to say the least and then it really feels bad that I cannot upvote. Please help me.
Today I am consistently seeing a Server Error message in Nodes To Consider where the keep/edit/reap/nada radio buttons would ordinarily be. LanX reports seeing the same.
The error reads like this:
Server Error (Error ID 4080294c3022)
An error has occurred. The site administrators
have been notified of the problem and will likely
soon fix it. We thank you, for you're patients.
but with the span also having style="color: #cc0000" being applied, so that line of text is in red. It is consistent - it appears to happen every time when visiting that page (although the Error ID changes each time). If I view the node under consideration itself then the radio buttons appear in the Approval Nodelet as usual.
<center> elements are being used in the divs with the class reputation. <center> has been rendered obsolete, deprecated in HTML 4 and XHTML 1.
Obsolete
This feature is obsolete. Although it may still work in some browsers, its use is discouraged since it could be removed at any time. Try to avoid using it.
I played around with some new code for the top bar and the menu. I removed the tables and used flex. It isn't perfect, but it might be a slight improvement.
Note:This, or something close to it, is what I originally posted. The code in the first one is different.
My OS is Debian 10 (Buster); my perl versions are 5.28.1 local and 5.16.3 or 5.30.0 on web host depending on the shebang.
No matter how hysterical I get, my problems are not time sensitive. So, relax, have a cookie, and a very nice day!
Hey Monks,
So, it's been awhile. On a whim I came here and tried to login. I had to reset my password.
Now, I know this is not really a super secret space and nobody is going to get my credit cards, but can I implore the site admins here to not email me my password via email.
Hopefully I don't need to get into why, but I'm willing to explain if needed.
JP (punklrokk)
I propose that this be added to the links at the top of Perl News for 2 reason:
It's a living resource and a chance for more interaction virtually
To encourage its use so that it better accomplishes the its purpose described in #1
Further more, making the linked text clearly indicate the benefit of clicking the link (for PM organizers and virtual lurkers alike) would help. I have no suggestion for the wording.
I’m looking at the Best Nodes page. Sections for Best Nodes of the Day, Month, and Year have 10, 10, and 20 entries, respectively, as expected. But Best Nodes of the Week shows only 6 entries, numbered 5 to 10. Looks like something has gone wrong somewhere.
Reading Re^10: XS.c: loadable library and perl binaries are mismatched (got handshake key 0xc100000, needed 0xc180000) I was encouraged to confirm what rgren925 reported. I constructed a reply with about 120kB in it and used the Preview button to check it. All of it was rendered and there was no warning (that I could see) that it was over the size limit for posting. When it was subsequently submitted it still rendered fine and it was only on a further navigation to the same node that it did truncate to ~64kB as I expected.
This is not great from a UX perspective. The preview should either warn about the size or truncate it like the final submission would do or (ideally IMHO) both. The full text could still be retained in the textarea for ease of editing.
Davorg has posted a piece on LinkedIn (sorry, don't know how to link to it!) saying "Almost 7,800 unanswered 'perl' questions on StackOverflow. Can you help to answer some of them?" and giving the link https://stackoverflow.com/questions/tagged/perl?tab=Unanswered. I am not surprised, as I have never found SO to be a helpful community. If we wish to drive Perl traffic to this site - I assume we do - might it be worth posting answers here & putting a link to the relevant node on SO?
Hello everyone. Is it possible to unparent tangents in threads? In the conversation of Expression form of map or grep, I answered a question as to why I cared about the number of lines. I replied here, and that created a tangent. Is it possible to unparent my reply and its replies into a new thread, maybe titled "I do not like scrolling" or something? It would be to keep the focus on the map/grep topic and let the new topic be its own thread.
In my mind, tangents could confuse some newer users.
I know this may be a bad thought or too much of a bother, but I would like to know. Please?
My OS is Debian 10 (Buster); my perl versions are 5.28.1 local and 5.16.3 or 5.30.0 on web host depending on the shebang.
No matter how hysterical I get, my problems are not time sensitive. So, relax, have a cookie, and a very nice day!
It mentions that TPF "... carries the legal responsibility for Perl 5 and Perl 6..", which is clearly out of date. Also the links are non-SSL. Not exactly something you want to note when going to donate, e.g. - it does redirect to https://donate.perlfoundation.org/, but not before you've already made a request to http.
My last note is a thought, would it be to remove the unnecessary clicks in our "Donate" link above, and just link from here to https://donate.perlfoundation.org/donate.html. Idk if Dan is on here, but that page should probably get a face lift so that it has some of the info that's on https://donate.perlfoundation.org and may be more suitable for direct linking.
The node 11118252 has a "special" link that contains a vertical bar (encoded as %7C).
This link has been constructed by specifying the full href, as choroba told me in a private message.
As the vertical bar cannot be used directly in a link at the monastery as it separates the location from the displayed text, it must be encoded in some way.
Trying to use the path IO::Uncompress::Gunzip#Transparent-=>-0%7C1 with some shortcut schemas gives interesting results:
<EDIT>
metacpan.org and search.cpan.org work just fine, when accessed with the original path component "as is".
The perdoc.perl.org example is misleading, as there are no anchors within the page.
</EDIT>
All the generated links (except the full href) have one thing in common: The percent sign becomes encoded as %25. It depends on the target side if this will be interpreted in a useful way.
I didn't find any documentation on how to include a hex encoded value in a link.
Obviously it is handled different in a full href.
Is this a bug or is it a feature?
If it's a feature, then another feature might be missing: including hex codes in a path.
