Skip to content

RSS parser script [NodeBB]

Customisation
47 2 13.9k 2
  • Sorry Mark you’re going to hate me here…

    I know you’re a busy man, I was just wondering if there was any advancement on the RSS parser script?

    I’m sure once it’s done you’ll be able to pull a few people over here to ‘download’ or for 'instructions’😉

    Many thanks

  • Sorry Mark you’re going to hate me here…

    I know you’re a busy man, I was just wondering if there was any advancement on the RSS parser script?

    I’m sure once it’s done you’ll be able to pull a few people over here to ‘download’ or for 'instructions’😉

    Many thanks

    @jac Hi. Yes, I’m going to be taking a look at this over the coming days. Thanks for the patience…

  • @jac Hi. Yes, I’m going to be taking a look at this over the coming days. Thanks for the patience…

    @phenomlab said in RSS parser script [NodeBB]:

    @jac Hi. Yes, I’m going to be taking a look at this over the coming days. Thanks for the patience…

    Great to hear! Many thanks 😁

  • @phenomlab said in RSS parser script [NodeBB]:

    @jac Hi. Yes, I’m going to be taking a look at this over the coming days. Thanks for the patience…

    Great to hear! Many thanks 😁

    @jac I spent three hours looking into this today and sadly it’s not a simple affair in the sense that I can’t reuse the older Flarum script. Essentially, it’s a rewrite but not the end of the world.

    I’ve finished most of this, but have hit a stumbling block with the newer API so will need to research further before we can be ready for an initial release.

    There are some dependencies also, but nothing too major. Essentially, you will require nodebb-plugin-write-api (listed as the Write API) plugin to be able to use this new script. It also (currently) requires PHP to be installed (although future versions will probably make use of Python.

  • @jac I spent three hours looking into this today and sadly it’s not a simple affair in the sense that I can’t reuse the older Flarum script. Essentially, it’s a rewrite but not the end of the world.

    I’ve finished most of this, but have hit a stumbling block with the newer API so will need to research further before we can be ready for an initial release.

    There are some dependencies also, but nothing too major. Essentially, you will require nodebb-plugin-write-api (listed as the Write API) plugin to be able to use this new script. It also (currently) requires PHP to be installed (although future versions will probably make use of Python.

    @phenomlab said in RSS parser script [NodeBB]:

    @jac I spent three hours looking into this today and sadly it’s not a simple affair in the sense that I can’t reuse the older Flarum script. Essentially, it’s a rewrite but not the end of the world.

    I’ve finished most of this, but have hit a stumbling block with the newer API so will need to research further before we can be ready for an initial release.

    There are some dependencies also, but nothing too major. Essentially, you will require nodebb-plugin-write-api (listed as the Write API) plugin to be able to use this new script. It also (currently) requires PHP to be installed (although future versions will probably make use of Python.

    Amazing work Mark, can’t thank you enough for all the effort that’s going into releasing this and making it compatible.

    It’s a shame you’ve ran into a few issues, but can’t thank you enough! If this does get released I don’t see why more users wouldn’t want to use it.

  • @phenomlab said in RSS parser script [NodeBB]:

    @jac I spent three hours looking into this today and sadly it’s not a simple affair in the sense that I can’t reuse the older Flarum script. Essentially, it’s a rewrite but not the end of the world.

    I’ve finished most of this, but have hit a stumbling block with the newer API so will need to research further before we can be ready for an initial release.

    There are some dependencies also, but nothing too major. Essentially, you will require nodebb-plugin-write-api (listed as the Write API) plugin to be able to use this new script. It also (currently) requires PHP to be installed (although future versions will probably make use of Python.

    Amazing work Mark, can’t thank you enough for all the effort that’s going into releasing this and making it compatible.

    It’s a shame you’ve ran into a few issues, but can’t thank you enough! If this does get released I don’t see why more users wouldn’t want to use it.

    @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.

  • @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.

    @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! 👏🏻

  • @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! 👏🏻

    @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.

    @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!

  • @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 No problems. Happy to help.

  • @jac No problems. Happy to help.

    @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. 🍾

  • @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 😁 will this be published on the node forum too?

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

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

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

    @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!

  • @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!

    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 😁.

  • 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 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.

    @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 😁.

  • @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 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 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 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.

    @phenomlab said in RSS parser script [NodeBB]:

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

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


Related Topics
  • 2 Votes
    1 Posts
    62 Views
    No one has replied
  • What’s going on with NodeBB?

    Performance nodebb script die
    20
    5 Votes
    20 Posts
    1k Views
    @cagatay The most reliable way to upgrade Node.js on Ubuntu depends on how you originally installed it. Method 1: Using NVM (Recommended) If you already use Node Version Manager (NVM), upgrading is simple. NVM allows you to keep both versions and switch between them if needed. Install Node 22: nvm install 22 Switch to Node 22: nvm use 22 Set it as your default: nvm alias default 22 Verify the change: node -v Method 2: Using NodeSource (PPA) If you installed Node.js via apt using the NodeSource repository, you need to update the repository script to point to the new version. Remove the old NodeSource list (optional but cleaner): sudo rm /etc/apt/sources.list.d/nodesource.list Download and run the NodeSource setup script for Node 22: curl -fsSL [https://deb.nodesource.com/setup_22.x](https://deb.nodesource.com/setup_22.x) | sudo -E bash - Install/Upgrade Node.js: sudo apt-get install -y nodejs Verify the installation: node -v Method 3: Using the ‘n’ Package If you have npm installed, you can use the n interactive manager. Clear the npm cache: sudo npm cache clean -f Install the ‘n’ helper: sudo npm install -g n Install Node 22: sudo n 22 Update your shell: hash -r Troubleshooting Permission Denied: If you see permission errors using Method 2 or 3, ensure you are using sudo. Path Issues: If node -v still shows version 20 after upgrading via NVM, restart your terminal or run source ~/.bashrc. Conflicts: Avoid mixing these methods. If you switch from apt to nvm, it is best to sudo apt remove nodejs first to avoid path conflicts.
  • Page control arrows for PWA

    Solved Customisation nodebb
    27
    25 Votes
    27 Posts
    9k Views
    @crazycells it is, yes - I think I’ll leave it as there is no specific PWA CSS classes I know of. Well, you could use something like the below, but this means multiple CSS files for different operating systems. /** * Determine the mobile operating system. * This function returns one of 'iOS', 'Android', 'Windows Phone', or 'unknown'. * * @returns {String} */ function getMobileOperatingSystem() { var userAgent = navigator.userAgent || navigator.vendor || window.opera; // Windows Phone must come first because its UA also contains "Android" if (/windows phone/i.test(userAgent)) { return "Windows Phone"; } if (/android/i.test(userAgent)) { return "Android"; } if (/iPad|iPhone|iPod/.test(userAgent) && !window.MSStream) { return "iOS"; } return "unknown"; // return “Android” - one should either handle the unknown or fallback to a specific platform, let’s say Android } Once you’re in that rabbit hole, it’s impossible to get out of it.
  • Composer options on nodebb

    Solved Configure nodebb
    8
    1
    3 Votes
    8 Posts
    1k Views
    @Panda You should be able to expose the CSS for these using F12 to get into console [image: 1686833368846-3591518c-e3a3-4ada-a43c-6b32a5e0359c-image.png] [image: 1686833399483-a2b8ed46-4157-4ff2-85f0-576543380107-image.png] That should then expose the element once selected [image: 1686833431032-89d9c545-a47a-40d1-98f4-80cf3b958e8f-image.png] Here’s the below CSS you need based on the screenshot provided. .composer .formatting-bar .formatting-group li[data-format="picture-o"], .composer .formatting-bar .formatting-group li[data-format="spoiler"] { display: none; }
  • Blinking text Effect

    Customisation nodebb text effect css
    3
    5 Votes
    3 Posts
    1k Views
    @phenomlab I love it too @phenomlab said in Blinking text Effect: Has that “broken neon light” look that you see in films. It’s exactly that, kind of old neon signs of bar or pubs a bit cyberpunk too
  • [NODEBB] Scroll Button

    Solved Customisation css javascript html scroll button
    7
    1
    0 Votes
    7 Posts
    2k Views
    @downpw ooops. Forgot that. Thanks for adding.
  • [NODEBB] Stats

    Unsolved Customisation plugin stats script
    20
    1
    2 Votes
    20 Posts
    4k Views
    @phenomlab said in [NODEBB] Stats: @jac or I land up fixing it I wouldn’t put it past you
  • NodeBB Design help

    Solved Customisation
    8
    3
    2 Votes
    8 Posts
    2k Views
    @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.