You can disregard this issue. I had made a change to create a custom login screen that required modifications to authentication.js. I was just copying an older version of this file from a previous installation, but it looks like it was updated since then and the old version was not compatible. I apologize for the confusion!
cbeible
@cbeible
Posts made by cbeible
-
RE: New users not working
-
RE: New users not working
I just noticed that I also have v2.6.1 running in a similar EC2 instance and that one is working fine. So I don't think that it's an EC2 problem. But I'll try installing on a local instance to see if that make a difference and report back.
-
RE: New users not working
I'm using v2.7.2. And this instance is running on an EC2 instance in trial mode.
-
New users not working
Hello,
I just tried adding a few new users (New Entity > user) to log in to jsreport, but none of them seem to be working. I keep getting returned to the login screen. I've tried setting different permissions for each one, but nothing seems to work. The only user ID I can use to log in is the "admin" account.
Do you have any suggestions?
-
RE: Drag and drop designer
Our company is evaluating jsreport for integration into our SaaS-based infrastructure monitoring tool. The #1 request we get from customers is a WYSIWYG editor for report creation. Are there any updates to offering this functionality in jsreport? Our company may even be willing to help fund this effort if it can be prioritized.
-
Module parse failed: Unexpected token
I've been attempting to recompile the jsreport-studio package (
npm run build
), but keep hitting a strange error that I cannot resolve:ERROR in ./src/client.js 77:18 Module parse failed: Unexpected token (77:18) You may need an appropriate loader to handle this file type. | const routes = getRoutes(window.Studio.routes) | > let component = <Router history={history}>{routes}</Router> | | ReactDOM.render( @ ./src/theme/font-awesome.config.prod.js (multi ./src/client.js font-awesome-webpack-4!./src/theme/font-awesome.config.prod.js) main[0]
I've been doing some research and found references to similar errors that all point to dependency issues with webpack and acorn. However, none of the fixes suggested seem to be working.
Do you have any thoughts on how to remedy this issue?
Thanks!
-
RE: UI Theme / Color Changes
Ah I see! Okay... I appreciate the explanation.
-
RE: UI Theme / Color Changes
I really appreciate the update!
Just to be clear, I don't need this to be a feature that is exposed in the UI as a fancy menu-driven option. I just want to be able to make manual updates the existing SCSS. However, it doesn't appear to be working. I have located the appropriate SCSS (ie Toolbar.scss in the jsreport-studio module) that I think I need to change, but chrome dev tools is showing each style with strange text like "__3D4ee" that is appended to all of the classes from Toolbar.scss. I thought maybe this was coming from a license restriction on the free version I downloaded for testing? If so, do you know if the paid versions of jsreport will allow me to manually edit the SCSS without restriction?
GREAT product, by the way! I'm excited to get this working in our environment! Thanks again!
-
UI Theme / Color Changes
Is there a way to easily customize the color theme of the UI itself? For example, can I change the toolbar at the top to a new color, or perhaps even white-label the logo for our company? I was able to identify the locations of the SCSS for the application, but none of the changes I make to them seem to do anything. I think I'm just missing something obvious.
Thanks in advance!