Search results

  1. danger@

    Manual pages online: RFD – share your thoughts on changes to design

    as I understand this thread I suggest you report this upstream through freebsd bugzilla or raise this issue on docs@ mailing list as this is beyond the scope of this forum.
  2. danger@

    Coding for MAN and PMAN markup

    it supports section number argument, but it was optional for man and mandatory for pman. I changed it to optional for both.
  3. danger@

    Coding for MAN and PMAN markup

    Man bbcode currently generates links to man pages of freebsd-base and ports, hence false.
  4. danger@

    pr coding: titles

    I guess you will have a better luck asking this at the XF community forums.
  5. danger@

    pr coding: titles

    curl is available as well as file_get_contents
  6. danger@

    pr coding: titles

    it would definitely be possible to implement it with php callbacks, however it requires some XenForo and php knowledge...if someone comes up with a working solution I can apply it.
  7. danger@

    Coding for MAN and PMAN markup

    I am not sure if I entirely understood your request, but I made a simple change to the pman bbcode, let me know if that is what you requested.
  8. danger@

    Solved XenForo 2.2.6 Patch 2 to fix embedded YouTube content

    I applied latest XF patch, hopefully it will resolve the issue.
  9. danger@

    FreeBSD Forums header area (above the Forums button) directing readers to oudated content (outdated Handbook, and so on)

    this is out of control of the forums administrators and should be reported via https://bugs.freebsd.org/bugzilla/
  10. danger@

    FreeBSD Forums header area (above the Forums button) directing readers to oudated content (outdated Handbook, and so on)

    the top freebsd menu links should be fixed now. if there are some other problems pointed out in this thread, please point those directly at me. It has been quite a few years since I set this part of the forums up.
  11. danger@

    Portion of what I'm typing gets blocked

    Indeed, I installed the new version a few days ago, but apparently it has some bugs still, we will need to wait for future updates and hopefully it will get better.
  12. danger@

    What happened in the forum?

    I have set the bg color to exactly what has been requested in the above post. Well, it is my freebsd.org committer's username. It originates to quite a distant past and it is actually an acronym of my real name ;)
  13. danger@

    What happened in the forum?

    if you suggest specific css changes I can have a look at it.
  14. danger@

    Solved Syntax highlighting feature of Forums' CODE=c tag doesn't work

    this should be fixed for the time being. Although, the colors are pretty bad in the freebsd theme...not sure why yet.
  15. danger@

    What happened in the forum?

    it just got into an RC stage today, but I guess it will take some additional time until it will be production ready. I will try to fix the built-in tag to support the optional tag.
  16. danger@

    What happened in the forum?

    happy now? :)
  17. danger@

    What happened in the forum?

    Hello everybody, sorry for the inconvenience, I started with an upgrade yesterday and then got distracted in the middle of the process with an other issue and forgot to finish and enable the forum.
  18. danger@

    Solved Many pkg: ...( php72-intl-7.2.17_2.txz | php72-xmlreader-7.2.17_2.txz )... :Not Found

    run pkg update first - it appears like your pkg catalogue is outdated, currently there is php 7.2.18 in the quarterly repository.
  19. danger@

    Thanks vs Reactions

    getopt you are trying to show a strong voice here, but we had over 1,300 active users in last 3 months and only 45 votes were cast in this poll. I do not see that as enough for changing "the constitution". And don't forget, this place is more meritocracy than a democracy; this is not to mean we...
Back
Top