Skip to content

RSS parser script [NodeBB]

Customisation
47 2 23.8k 2
  • JAC JAC

    @phenomlab said in RSS parser script [NodeBB]:

    @jac ok, I spent some more time (another 2 hours) looking into this, and now have it working

    unknown.png
    unknown-1.png
    unknown-2.png

    Essentially, it works fine, but the issue here is that there is no text - it’s just videos. Looking at the structure of the XML file, it’s not the same as a standard RSS or ATOM file.

    Proving difficult. Work continues…

    I’ll keep you posted.

    Wow!!!

    Absolute genius! 🤝 👏

    The work continues for you, but absolutely amazing work Mark! 👏🏻

    wrote on last edited by
    #8

    @jac thanks. I think I’ve found a way to get the description of the YouTube video from the XML structure in the URL, but this may cause issues with other URLs that are in fact RSS and atom compliant.

    I’ll look at this a bit more tomorrow.

  • @jac thanks. I think I’ve found a way to get the description of the YouTube video from the XML structure in the URL, but this may cause issues with other URLs that are in fact RSS and atom compliant.

    I’ll look at this a bit more tomorrow.

    wrote on last edited by
    #9

    @phenomlab said in RSS parser script [NodeBB]:

    @jac thanks. I think I’ve found a way to get the description of the YouTube video from the XML structure in the URL, but this may cause issues with other URLs that are in fact RSS and atom compliant.

    I’ll look at this a bit more tomorrow.

    Thanks very much mate for all the hard work especially on a weekend, it’s very much appreciated!

  • JAC JAC

    @phenomlab said in RSS parser script [NodeBB]:

    @jac thanks. I think I’ve found a way to get the description of the YouTube video from the XML structure in the URL, but this may cause issues with other URLs that are in fact RSS and atom compliant.

    I’ll look at this a bit more tomorrow.

    Thanks very much mate for all the hard work especially on a weekend, it’s very much appreciated!

    wrote on last edited by
    #10

    @jac No problems. Happy to help.

  • @jac No problems. Happy to help.

    wrote on last edited by
    #11

    @phenomlab said in RSS parser script [NodeBB]:

    @jac No problems. Happy to help.

    Many thanks mate, looking forward to its release, it’ll really make a great difference importing match interviews, highlights etc. 🍾

  • JAC JAC

    @phenomlab said in RSS parser script [NodeBB]:

    @jac No problems. Happy to help.

    Many thanks mate, looking forward to its release, it’ll really make a great difference importing match interviews, highlights etc. 🍾

    wrote on last edited by
    #12

    @jac 😁 will this be published on the node forum too?

  • JAC JAC

    @jac 😁 will this be published on the node forum too?

    wrote on last edited by
    #13

    @jac Possibly. Ideally as a plugin though if that does happen

  • @jac Possibly. Ideally as a plugin though if that does happen

    wrote on last edited by
    #14

    @phenomlab said in RSS parser script [NodeBB]:

    @jac Possibly. Ideally as a plugin though if that does happen

    Fantastic! Can’t wait 😁 it will be a fantastic addition!

  • JAC JAC

    @phenomlab said in RSS parser script [NodeBB]:

    @jac Possibly. Ideally as a plugin though if that does happen

    Fantastic! Can’t wait 😁 it will be a fantastic addition!

    wrote on last edited by
    #15

    Does this plugin currently work fine but you’re trying to develop it to pull in descriptions otherwise it would be bad for SEO etc?

    Is that right 🤔.

    I’m looking forward to its release as you know 😁.

  • JAC JAC

    Does this plugin currently work fine but you’re trying to develop it to pull in descriptions otherwise it would be bad for SEO etc?

    Is that right 🤔.

    I’m looking forward to its release as you know 😁.

    wrote on last edited by
    #16

    @jac Yes, pretty much that. The only part left to develop is the feed you provided me. It’s structured differently meaning I have to fetch the data from a large array, and it takes time to identify which array key holds the specific string you want.

    For other RSS and ATOM feeds it’ll work out of the box. However, it (currently) requires PHP and MySQL (as it was ported from Flarum) and ideally should be moved to native NodeJS and MongoDB. Sadly, work commitments mean I haven’t had as much time as I’d like to update all of this so inevitably, the release has been delayed.

  • @jac Yes, pretty much that. The only part left to develop is the feed you provided me. It’s structured differently meaning I have to fetch the data from a large array, and it takes time to identify which array key holds the specific string you want.

    For other RSS and ATOM feeds it’ll work out of the box. However, it (currently) requires PHP and MySQL (as it was ported from Flarum) and ideally should be moved to native NodeJS and MongoDB. Sadly, work commitments mean I haven’t had as much time as I’d like to update all of this so inevitably, the release has been delayed.

    wrote on last edited by
    #17

    @phenomlab said in RSS parser script [NodeBB]:

    @jac Yes, pretty much that. The only part left to develop is the feed you provided me. It’s structured differently meaning I have to fetch the data from a large array, and it takes time to identify which array key holds the specific string you want.

    For other RSS and ATOM feeds it’ll work out of the box. However, it (currently) requires PHP and MySQL (as it was ported from Flarum) and ideally should be moved to native NodeJS and MongoDB. Sadly, work commitments mean I haven’t had as much time as I’d like to update all of this so inevitably, the release has been delayed.

    Thanks for the update Mark, all sounds very interesting and of course promising, and I eagerly await it’s release 😁.

  • JAC JAC

    @phenomlab said in RSS parser script [NodeBB]:

    @jac Yes, pretty much that. The only part left to develop is the feed you provided me. It’s structured differently meaning I have to fetch the data from a large array, and it takes time to identify which array key holds the specific string you want.

    For other RSS and ATOM feeds it’ll work out of the box. However, it (currently) requires PHP and MySQL (as it was ported from Flarum) and ideally should be moved to native NodeJS and MongoDB. Sadly, work commitments mean I haven’t had as much time as I’d like to update all of this so inevitably, the release has been delayed.

    Thanks for the update Mark, all sounds very interesting and of course promising, and I eagerly await it’s release 😁.

    wrote on last edited by
    #18

    @jac said in RSS parser script [NodeBB]:

    @phenomlab said in RSS parser script [NodeBB]:

    @jac Yes, pretty much that. The only part left to develop is the feed you provided me. It’s structured differently meaning I have to fetch the data from a large array, and it takes time to identify which array key holds the specific string you want.

    For other RSS and ATOM feeds it’ll work out of the box. However, it (currently) requires PHP and MySQL (as it was ported from Flarum) and ideally should be moved to native NodeJS and MongoDB. Sadly, work commitments mean I haven’t had as much time as I’d like to update all of this so inevitably, the release has been delayed.

    Thanks for the update Mark, all sounds very interesting and of course promising, and I eagerly await it’s release 😁.

    Just checking in on this, is there any advancement? 👍🏻

  • JAC JAC

    @jac said in RSS parser script [NodeBB]:

    @phenomlab said in RSS parser script [NodeBB]:

    @jac Yes, pretty much that. The only part left to develop is the feed you provided me. It’s structured differently meaning I have to fetch the data from a large array, and it takes time to identify which array key holds the specific string you want.

    For other RSS and ATOM feeds it’ll work out of the box. However, it (currently) requires PHP and MySQL (as it was ported from Flarum) and ideally should be moved to native NodeJS and MongoDB. Sadly, work commitments mean I haven’t had as much time as I’d like to update all of this so inevitably, the release has been delayed.

    Thanks for the update Mark, all sounds very interesting and of course promising, and I eagerly await it’s release 😁.

    Just checking in on this, is there any advancement? 👍🏻

    wrote on last edited by
    #19

    @jac Still on my list. Going to be looking at this hopefully soon.

  • @jac Still on my list. Going to be looking at this hopefully soon.

    wrote on last edited by
    #20

    @phenomlab said in RSS parser script [NodeBB]:

    @jac Still on my list. Going to be looking at this hopefully soon.

    👏🏻👏🏻🤞🏻 Can’t wait pal!!

  • JAC JAC

    @phenomlab said in RSS parser script [NodeBB]:

    @jac Still on my list. Going to be looking at this hopefully soon.

    👏🏻👏🏻🤞🏻 Can’t wait pal!!

    wrote on last edited by
    #21

    @jac said in RSS parser script [NodeBB]:

    @phenomlab said in RSS parser script [NodeBB]:

    @jac Still on my list. Going to be looking at this hopefully soon.

    👏🏻👏🏻🤞🏻 Can’t wait pal!!

    Any update mate? 🤝😉

  • JAC JAC

    @jac said in RSS parser script [NodeBB]:

    @phenomlab said in RSS parser script [NodeBB]:

    @jac Still on my list. Going to be looking at this hopefully soon.

    👏🏻👏🏻🤞🏻 Can’t wait pal!!

    Any update mate? 🤝😉

    wrote on last edited by
    #22

    @jac Not yet. Sorry. Still on my list, but take comfort in the fact that it’s 75% completed 🙂

  • @jac Not yet. Sorry. Still on my list, but take comfort in the fact that it’s 75% completed 🙂

    wrote on last edited by
    #23

    @phenomlab said in RSS parser script [NodeBB]:

    @jac Not yet. Sorry. Still on my list, but take comfort in the fact that it’s 75% completed 🙂

    Brilliant mate, can’t wait! 😁😁😁😁😁😁

  • JAC JAC

    @phenomlab said in RSS parser script [NodeBB]:

    @jac Not yet. Sorry. Still on my list, but take comfort in the fact that it’s 75% completed 🙂

    Brilliant mate, can’t wait! 😁😁😁😁😁😁

    wrote on last edited by JAC
    #24

    @jac said in RSS parser script [NodeBB]:

    @phenomlab said in RSS parser script [NodeBB]:

    @jac Not yet. Sorry. Still on my list, but take comfort in the fact that it’s 75% completed 🙂

    Brilliant mate, can’t wait! 😁😁😁😁😁😁

    Any update on this mate? I know you’re a busy man! 😁.

  • JAC JAC

    @jac said in RSS parser script [NodeBB]:

    @phenomlab said in RSS parser script [NodeBB]:

    @jac Not yet. Sorry. Still on my list, but take comfort in the fact that it’s 75% completed 🙂

    Brilliant mate, can’t wait! 😁😁😁😁😁😁

    Any update on this mate? I know you’re a busy man! 😁.

    wrote on last edited by
    #25

    @jac sorry for the delay. Just finishing up helping @DownPW with a project and you’re next in the list 👍

  • @jac sorry for the delay. Just finishing up helping @DownPW with a project and you’re next in the list 👍

    wrote on last edited by
    #26

    @phenomlab said in RSS parser script [NodeBB]:

    @jac sorry for the delay. Just finishing up helping @DownPW with a project and you’re next in the list 👍

    Many thanks mate 😁

  • JAC JAC

    @phenomlab said in RSS parser script [NodeBB]:

    @jac sorry for the delay. Just finishing up helping @DownPW with a project and you’re next in the list 👍

    Many thanks mate 😁

    wrote on last edited by JAC
    #27

    @phenomlab I know you’re a busy man of course mate, just doing my weekly post update 😉.


Related Topics
  • Nodebb design

    Solved General nodebb
    2
    1 Votes
    2 Posts
    1k Views
    phenomlab
    @Panda said in Nodebb design: One negative is not being so good for SEO as more Server side rendered forums, if web crawlers dont run the JS to read the forum. From recollection, Google and Bing have the capability to read and process JS, although it’s not in the same manner as a physical person will consume content on a page. It will be seen as plain text, but will be indexed. However, it’s important to note that Yandex and Baidu will not render JS, although seeing as Google has a 90% share of the content available on the web in terms of indexing, this isn’t something you’ll likely lose sleep over. @Panda said in Nodebb design: The “write api” is preferred for server-to-server interactions. This is mostly based around overall security - you won’t typically want a client machine changing database elements or altering data. This is why you have “client-side” which could be DOM manipulation etc, and “server-side” which performs more complex operations as it can communicate directly with the database whereas the client cannot (and if it can, then you have a serious security flaw). Reading from the API is perfectly acceptable on the client-side, but not being able to write. A paradigm here would be something like SNMP. This protocol exists as a UDP (UDP is very efficient, as it is “fire and forget” and does not wait for a response like TCP does) based service which reads performance data from a remote source, thus enabling an application to parse that data for use in a monitoring application. In all cases, SNMP access should be “RO” (Read Only) and not RW (Read Write). It is completely feasible to assume complete control over a firewall for example by having RW access to SNMP and then exposing it to the entire internet with a weak passphrase. You wouldn’t do it (at least, I hope you wouldn’t) and the same ethic applies to server-side rendering and the execution of commands.
  • adding some console.log to Nodebb

    Solved Customisation nodebb
    4
    1 Votes
    4 Posts
    2k Views
    phenomlab
    @eeeee if you’re using the console, you could try node app.js > app.log 2>&1 This would redirect stdout to a file named app.log and redirect stderr to stdout. I’m not sure about standard logging under NodeBB, but there is an error log located at logs/error.log. Failing that, you could always stop the NodeBB service then use ./nodebb dev from the console which would then provide debug output.
  • NodeBB: The global Search option

    Solved Configure search nodebb
    5
    0 Votes
    5 Posts
    2k Views
    phenomlab
    @mventures Yes, exactly. The other icon will restart NodeBB whilst the first icon I referenced will rebuild (recompile) it. The huge strength of NodeBB over Flarum (for example) is that the code is precompiled, and called once at boot. PHP’s code has to repeatedly reload code from source making it much slower.
  • Bootstrap Version

    Solved Customisation nodebb bootstrap
    8
    5 Votes
    8 Posts
    3k Views
    Madchatthew
    @phenomlab That will be nice once they have completed that. It will be interesting to see how long that takes. So for now I will use custom css to make it look the way I want. Frameworks just make things a little faster. Thanks @phenomlab
  • [NODEBB] Welcome Message

    Solved Customisation css html nodebb
    20
    2
    13 Votes
    20 Posts
    9k Views
    phenomlab
    @DownPW the ‘js’ code for the banner takes the time from the client, so what it displays really depends on the regional settings for the operating system. I’ve not seen this issue myself but would like to see some examples of screenshots if possible.
  • [NodeBB] username cards

    Solved Customisation nodebb
    8
    5 Votes
    8 Posts
    3k Views
    Sampo2910
    @phenomlab Aha…nice to know. As always thank you for the reply and information.
  • Social icon (Nodebb)

    Solved Customisation nodebb social
    7
    0 Votes
    7 Posts
    3k Views
    JAC
    @phenomlab said in Social icon (Nodebb): @jac I just tested my theory around using the OG image, and according to the Twitter card validator, it works fine [image: 73e805e1-997b-41bf-9259-51c5052ca8fc-image.png] fixed
  • NodeBB Design help

    Solved Customisation
    8
    3
    2 Votes
    8 Posts
    4k Views
    phenomlab
    @riekmedia I’ve applied some new CSS to your site. Can you reload the page and try again ? For the record, this is what I added #footer { background: #2d343e; border-top: 4px solid #2d343e; font-size: 0.9em; margin-top: 70px; padding: 80px 0 0; position: relative; clear: both; bottom: 0; left: 0; right: 0; z-index: 1000; margin-left: -15px; margin-right: -338px; } The /categories page seems a bit messed up, so looking at that currently EDIT - issued some override CSS in the CATEGORIES widget <!--- CSS fix for overspill on /categories page - DO NOT DELETE --> <style> #footer { margin-right: -45px; } </style> That should resolve the /categories issue.