I am integrating ngx-admin(3.0.0) with jhipster. It's not loading the dashboard and showing spinner only.
I followed https://github.com/fstepho/dashboard to do the upgrade.
Committed my code to https://github.com/chaitut715/dashboard
There are no error messages.
Related
I downloaded the repo from rule-node-examples-ui-ngx, tried following the instructions and did yarn install and yarn start.
Managed to get it to compile and start at http://localhost:5000 but in my browser I'm getting a 404 error saying 'Cannot GET /'.
What am I doing wrongly? The documentation isn't really clear on this and I can't seem to find a lot of existing help out there on the topic. Is this not a standalone application and requires another application to run?
I have looked at the ThingsBoard documentation, which suggests I have to access this application's UI via the ThingsBoard hot-redeploy mode. Hoping someone can provide some clarity on this. Btw I'm trying to get the custom rule nodes running on the pre-prepared Thingsboard Docker image, which is why I have yet to try out the option in this ThingsBoard documentation
I'm having some trouble deploying my .sppkg file to Sharepoint 2019. I've developed it using the SPFx framework version v1.4.1 to ensure it is compatible, and the webpart works fine when deployed in development mode against the Sharepoint environment's workbench (https://your-sharepoint-site/_layouts/workbench.aspx).
However, after uploading the webpart to the app catalog, it displays the general error message :
Error in client-side code
and is unable to deploy. In the logs for the Sharepoint environment, after uploading the package this error appears:
Caught an exception while updating the properties of SharePoint App package AppCatalog/my-webpart-app.sppkg. Error: There were errors when validating the App package: Error in the application. Stack Trace:
at Microsoft.SharePoint.Marketplace.CorporateCuratedGallery.SPCorporateCatalogEventReceiver.PromoteProperties(SPListItem listItem, Stream packageStream, Boolean addingPackage)
at Microsoft.SharePoint.Marketplace.CorporateCuratedGallery.SPCorporateCatalogEventReceiver.HandleItemAddedOrUpdated(SPListItem listItem, Boolean categoryChanged, Boolean addingPackage, Boolean isDeploying, Boolean beforeIsDeployed, Boolean beforeIsCurrentVersionDeployed)
The same package deploys fine in a Sharepoint Online environment. I don't have another 2019 environment to test in.
I'm a bit at a loss of how to debug. A test .sppkg file built from the starter SPFx project using version 1.4.1 deploys just fine, so my only thought is to slowly add functionality to the base package and deploy new versions until it breaks, but that feels a bit like madness.
Does anyone have any insight into what part of the packaging process might cause the .sppkg file to be unable to run when uploaded? Could it be permissioning issues in the environment?
Metadata of you .sppkg has errors:
There were errors when validating the App package: Error in the application.
I think, main error - you not create clean project. Create clean project, by using this info
yo #microsoft/sharepoint
Don't mistake, answer this question:
Which baseline packages do you want to target for your component(s)?
There are 2016, 2019, SharePoint Online only (latest)
If your package was created for sharepoint online - it not be added to sharepoint 2019 On Premis.
Permissions errors you will see in app catalog, and uls logs. Your error - incorrect metadata of package.
Sharepoint starter kit has this info
Starter Kit Version 1 includes a comprenshive strategy for only SharePoint Online, as well as a single SPFx solution that encapsulates all webparts and extensions into a single package. Version 1 may be accessed via the v1 branch for legacy purposes and will not be maintained beyond April 2020. link
so, don't modify it:) it's alredy legacy.
For developer own packages on premises - you can create single server farm. If you work in sharepoint online - you can use Office 356 developer programm
I'm new to LifeRay development still learning the ropes so please bear with me.
I created only the shell of an npm react portlet using the blade cli template, I'm using LifeRay CE 7.0.4 GA5 with mySql database.
After doing a few tries getting the right dependencies i was able to deploy it. And i get this message back from the console:
04:20:26,149 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][AutoDeployDir:252] Processing com.st.npm.react-1.0.0.jar
04:20:33,151 INFO [fileinstall-C:/liferay-ce-portal-7.0-ga5/osgi/modules][BundleStartStopLogger:38] STOPPED com.st.npm.react_1.0.0 [520]
04:20:33,858 INFO [Refresh Thread: Equinox Container: 706ebb15-e5df-0018-1059-8ffb03af5e89][BundleStartStopLogger:35] STARTED com.st.npm.react_1.0.0 [520]
And just to be safe i ran diag on the new bundle deployed in gogo shell and looks good, no errors showing up.
My problem is that i don't see it displayed under applications > sample category to add it to a page. Is there anything I'm missing here?
Here is my project:
https://github.com/JAlonsoHdz/NPM_React.git
I just tried to open my project on expo after making some changes to my backend code, now I am getting a No App Configuration Data message and I am unable to do anything. I am not seeing any errors in my console, only warnings. The change I made to my backend shouldn't impact my app's configuration. I just added values to a model and updated a controller for those values. I "Reset Content and Settings" on my simulator and did another npm install to update my packages and still having this issue.
I am trying to refresh a control (by id 'previewPane') in 'onComplete' event of an action button using:
XSP.partialRefreshPost('#{id:previewPane}').
It works fine on my test server Domino 9.0.1(not on bluemix).
On Bluemix it is throwing the error:
"CLFAD0380E: No component found with ID
$$xspsubmitid=view:_id1:previewPane to handle the submit event".
Is there a way to fix this.
Thanks
This is due to feature enhancement work in this area and associated function. It is specific to the current XPages Buildpack release on Bluemix, hence the reason that it is not effecting your test Domino 9.0.1 server.
You can suppress the validation error message handling by including the following XSP property in your application's xsp.properties file and redeploying to Bluemix:
xsp.error.disable.0380=true
An upcoming release of the XPages Buildpack will include the full enhancement and attempt to resolve the current regression you are experiencing.