Quantcast
Channel: Superdesk Development Discussions on Sourcefabric Forum
Viewing all 288 articles
Browse latest View live

Unable to load Desk "Monitoring settings"

$
0
0
Hi,
I'm on the latest superdesk master. Have created a few desks, and when I get to the Admin --> settings --> Decks and select a Desk
Select action 'Monitoring settings' breaks with this stack.
at HTMLButtonElement.<anonymous> (app.bundle.50794ea7.js:179)
at HTMLButtonElement.dispatch (app.bundle.50794ea7.js:24)
at HTMLButtonElement.g.handle (app.bundle.50794ea7.js:24)
Thanks.

MOS in Superdesk

$
0
0

Hello Super Team,


We have recently installed a cloud instance of Superdesk and superdesk publisher and have since been learning about the CMS for the purpose of integrating it as part of an end-end  platform we are currently building to serve a community of broadcasters in their news & programming exchange.  The platform also includes a video centric MAM, media serverGraphics & an Automation apps. 


Ultimately our aim is to adopt Superdesk as the core News CMS. 

 

While we understand the challenges of adopting and adapting superdesk as a broadcast operation NRCS  we are also confident that it will genuinely be a game changer to the broadcast newsroom who are used to NRCSs that are usually studio operations centric rather than community centric.

 

We are mindful of the adaptation challenges to the broadcast environment with the lack of a run-down (running order) structures  and interface with Graphics, studio automation such as tele-prompter, video player etc but we think these are fixable once the CMS becomes MOS compliant. 

At this very moment our target is;

  1. Complete the installation of the CMS other components namely (Planning, utilities) and integrating with Live Blog.
  2. Integrate Superdesk with the MAM application.                    Is this is something the super team can help us with at this stage?  We would very much appreciate that.

 

Learning to Ingest in Superdesk

$
0
0
I am facing two challenges 
1- I set up a number of RSS feeds ingest. I created a desk for the RSS Feeds and a stage for each of the feeds. Then routed each feed into its coresponding  stage They all are ingesting fine but when I launch monitoring widget in my workspace for any stage  I get either;
 A- Empty widget window
 B- Content of another feed although the monitoring widget stage name is correct.

2- Ingesting Email:
I am trying to add a new source. I fill in all the details but the save button will not turn blue. Also Is the email server default a SMTP or IMAP?

HAs anyone seen this before?

$
0
0
The server response is shown below from an admin account. This was working fine 

Does this mean there is an issue with the installation itself?

Help needed with Superdesk re-installation on a Cloud server

$
0
0
HI,

I am looking for help from someone versed with the installation of Superdesk on a hosted virtual cloud machine. 

Ingestion error

$
0
0
I am seeing this in the log when trying to ingest an NITF-message using the NITFparser in Superdesk






p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #000000; background-color: #ffffff}
span.s1 {font-variant-ligatures: no-common-ligatures}



Error while parsing fishing-test-pure-iptc-1.xml: expected '}' before end of string level=ERROR process=ForkPoolWorker-1



Upgrading superdesk

$
0
0
Hi,

what are the steps for upgrading superdesk? I have an instance 1.14 which I assume is ready for an upgrade (or three)

Trond

Number of images to upload

$
0
0
Are there any restrictions on number of images to upload and/or attach / reference to an article?

I have a client who would like to have the possibility to upload at least 20 images/files and if possible have a restriction on max 40 images/files.

I tried to see if there were any settings for this in the GUI, but I couldn't find any.

I am assuming it could be possible, but at the same time allowing for so many files to upload could cause a timeout of some sort.

Superdesk install script

$
0
0
I don't know if there's any need or use but I did modify the current script for a fresh install on Ubuntu 19.10. It's still imperfect and needs some testing. Currently set to install off the master branch with publisher and analytics (unless I totally missed something). Currently no simple setup for domain name and mail settings.

I have my script and an email address at bmg.dirigo.us

Feedback is welcome of course.

PHP now supported by Google App Engine (versus Google Compute Engine)

Installing latest on 16.04

$
0
0
Here are some findings when you install superdesk latest version in 1.x branch 

1) Login to your fresh ubuntu 16.04
2) change to root (sudo -i is my preferred command).
3) run the install script:

curl -s https://raw.githubusercontent.com/superdesk/fireq/files/superdesk/install | sudo bash

When superdesk-install comes to node installation you will see this warning:
================================================================================
================================================================================

                              DEPRECATION WARNING                            

  Node.js 7.x is no longer actively supported!

  You will not receive security or critical stability updates for this version.

  You should migrate to a supported version of Node.js as soon as possible.
  Use the installation script that corresponds to the version of Node.js you
  wish to install. e.g.

   * https://deb.nodesource.com/setup_10.x — Node.js 10 LTS "Dubnium"
   * https://deb.nodesource.com/setup_12.x — Node.js 12 LTS "Erbium" (recommended)
   * https://deb.nodesource.com/setup_14.x — Node.js 14 LTS "Fermium"

  Please see https://github.com/nodejs/Release for details about which
  version may be appropriate for you.

  The NodeSource Node.js distributions repository contains
  information both about supported versions of Node.js and supported Linux
  distributions. To learn more about usage, see the repository:

================================================================================
================================================================================

I decided to ignore it.

Using the command you will get some errors when it comes to npm.
ERROR: wooper 0.4.2 has requirement requests==2.3.0, but you'll have requests 2.23.0 which is incompatible.
ERROR: eve 0.7.8 has requirement werkzeug<=0.11.15,>=0.9.4, but you'll have werkzeug 0.16.1 which is incompatible.
ERROR: requests-oauthlib 1.3.0 has requirement oauthlib>=3.0.0, but you'll have oauthlib 2.1.0 which is incompatible.

And you will get a lot of warnings when it installs npm packages which all are deprecated.
(to many to paste)

On 16.04 all this worked "perfectly". 
If you are on Azure or AWS you need to open some ports in order to get access to your newly installed Superdesk. 
I opened: 
Inbound: 
80, 443, 5000, 5555 and 9000 
25, 587 (for mail)
20,21,4242,4243 (for ftp)
22 (for ssh)

outbound:
80,443,9000
25,587


Removing Vocabularies

$
0
0
Hi,

I added one vocabulary just for test. How do I remove it?

Also:
I accidentally overwrote the original subject list. How to restore? 

Installing Planning Component

$
0
0
Hi all,

I have tried to install the planning component on my newly freshly installed superdesk installation. I have followed this Readme instruction for installing:


I believe I have completed all steps, but when logging in I cannot see any sights of planning. I have also restarted the superdesk service just in case.

Looking forward to hearing from someone.

Trond

Install script fails on fresh Ubuntu 16.04

$
0
0
I put Ubuntu 16.04 on an Oracle VM Virtualbox, and entered this code:
I get this error and get kicked to prompt after the postbuild script:
14 verbose stack Error: superdesk-core@1.33.2 setup-extensions: `node ./tasks/namespace-css-from-extensions.js && node ./tasks/install-extensions.js`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:279:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:194:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:194:7)
14 verbose stack     at maybeClose (internal/child_process.js:899:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid superdesk-core@1.33.2
16 verbose cwd /opt/superdesk/client/node_modules/superdesk-core
17 error Linux 4.15.0-45-generic
18 error argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "setup-extensions"
19 error node v7.10.1
20 error npm  v4.2.0
21 error code ELIFECYCLE
22 error errno 1
23 error superdesk-core@1.33.2 setup-extensions: `node ./tasks/namespace-css-from-extensions.js && node ./tasks/install-extensions.js`
23 error Exit status 1
24 error Failed at the superdesk-core@1.33.2 setup-extensions script 'node ./tasks/namespace-css-from-extensions.js && node ./tasks/install-extensions.js'.
24 error Make sure you have the latest version of node.js and npm installed.
24 error If you do, this is most likely a problem with the superdesk-core package,
24 error not with npm itself.
24 error Tell the author that this fails on your system:
24 error     node ./tasks/namespace-css-from-extensions.js && node ./tasks/install-extensions.js
24 error You can get information on how to open an issue for this project with:
24 error     npm bugs superdesk-core
24 error Or if that isn't available, you can get their info via:
24 error     npm owner ls superdesk-core
24 error There is likely additional logging output above.
25 verbose exit [ 1, true ]
26 warn Local package.json exists, but node_modules missing, did you mean to install?
Any tips on how to resolve this?

Grunt - concatenated

$
0
0
When you run grunt build you will eventually see this:

Template "/opt/superdesk/client/node_modules/superdesk-core//opt/superdesk/client/node_modules/superdesk-core/tasks/options/ngtemplates.js" not found.

The fix is:

change: 
index: {
        cwd: '<%= coreDir %>',
        dest: './index.html',
        src: __filename, // hack to make ngtemplate work
        options: {
            bootstrap: () => {
                const features = getConfig().features || {};
                const buildIndex = require('../../index.html.js');

                return buildIndex(features);
            },
        },
    },


to:

index: {
        cwd: '<%= coreDir %>',
        dest: './index.html',
        src: src, // __filename, // hack to make ngtemplate work
        options: {
            bootstrap: () => {
                const features = getConfig().features || {};
                const buildIndex = require('../../index.html.js');

                return buildIndex(features);
            },
        },
    },

and:
(on line 74):
src: src, // __filename, // hack to make ngtemplate work

Start client server failes

$
0
0
Hi all! 
I tried to setup Liveblog locally on a fresh Ubuntu 16.04 machine. Everything worked fine but when I tried to start the client server with the following command I get an error: 
grunt --force server --server='http://localhost:5000/api' --ws='ws://localhost:5100'

This is the error I get: 

ERROR in ./node_modules/css-loader!./node_modules/sass-loader/lib/loader.js!./node_modules/superdesk-core/scripts/apps/authoring/styles/multiedit.scss
Module build failed: Error: ENOENT: no such file or directory, scandir '/home/fabiangeissler/Desktop/liveblog-master/client/node_modules/node-sass/vendor'

Although the complete error message is quite long, so I pasted it into a GhostBin which is available with the following link: https://ghostbin.co/paste/fff9j

I downloaded the Source Code as zip of version 3.8.1 from this link: https://github.com/liveblog/liveblog/releases

Does anybody has the same issue with the latest version or maybe already found a workaround for this issue? 

Thanks for any help!

BR,
Fabian

Superdesk serve over HTTPS

$
0
0
Hello!

I have managed to set up a superdesk instance (not development) using the instructions from here:

It seems this doc may be slightly outdated since I was able to use this command and it automates the whole process including publisher. 

The current issue I am having is that I cannot access the site after I have deployed an SSL cert (I can access it via the public IP). The error in console is a mixed content error. I can, however, access the contentapi as this seems to accept https. 

I'd prefer not to access via the IP. Any insights into how I can serve SuperDesk over https would be greatly appreciated!

Freelance Developer

$
0
0
Hello,
We are a small news organization hoping to expand.

We are seeking a full stack developer who would be able to work with on this project. 

If there is anyone on here who might be interested please let us know

Thanks

Language tools / spell checkers

Subject codes in superdesk.json

$
0
0
For anyone interested I have an XSL tranformation from IPTC subject Codes to Superdesk Vocabs-format available. Even have the subject code file available as well. In English that is.

The transformation might also work on Media Topics as I have used the NewsMLG2 - Knowledge Item as base for the transformation.

Trond
 
Viewing all 288 articles
Browse latest View live