With our headless CMS we provide enterprise-grade solutions for businesses of all size.
var myContent = SenseNet.ContentRepository.Content.Load(path);
myContent.RebuildIndex(true, SenseNet.ContentRepository.Storage.Search.IndexRebuildLevel.DatabaseAndIndex);
yes that was the case
messed up index
When will hacktober swags will dispatch
Hi, I have installed sensenet services and sensenet webpages. After building the application, when I tried to navigate to Root/Sites/Default_Site on localhost, I get this error: "Couldn't load /Root/System/SystemPlugins/Portlets/AdvancedLogin/LoginView"
when i checked event viewer got this error message
Message: http://server/Root/System/SystemPlugins/Portlets/AdvancedLogin/LoginView.ascx(41): error CS0012: The type 'IIdentity' is defined in an assembly that is not referenced. You must add a reference to assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'.
please help
Hi, Our sensenet server is on http://localhost:8080 and client(React-Redux) is running on http://localhost:3000. We are facing issue while we connect the client to the server through API? Is it possibile? getting 500 Internal Server Error, Any suggestions
Stack: "Error: Unknown action. Action: RegisterUser
at Repository.<anonymous> (http://localhost:3000/main.bundle.js:1633:27)
at Generator.throw (<anonymous>)
at rejected (http://localhost:3000/vendors~main.bundle.js:177019:65)"
at Repository.<anonymous> (http://localhost:3000/main.bundle.js:1633:27)
at Generator.throw (<anonymous>)
at rejected (http://localhost:3000/vendors~main.bundle.js:177019:65)"
Hi @sibinkara , 'RegisterUser' action is not the part of the sensenet core package (which is available on github) but a custom action for our DMS mvp app. There's a public github repository with the import source package with the additional DMS demo content and features here https://github.com/SenseNet/sn-demoinstall-demo but it is not offical and it is not supported
@herflis One more question when we try to connect from http://locathost:3000 to https://devservice.demo.sensenet.com/ client gets connected.
when we try to connect from http://locathost:3000 to http://localhost:8080/ getting 404 (http://localhost:8080/sn-token/login), we also tried https://localhost:443 got the same error 404, How to resolve this issue, Any settings to do on server side?
when we try to connect from http://locathost:3000 to http://localhost:8080/ getting 404 (http://localhost:8080/sn-token/login), we also tried https://localhost:443 got the same error 404, How to resolve this issue, Any settings to do on server side?
@tusmester I'm in the process of upgrading my old tools based on https://github.com/SenseNet/sn-client-dotnet to use the Nuget Package
All still work fine on my still old SN6 release that I'm on
but it's complaining about ClientContext.Initialize(ServerContext[]) is obsolete Add servers using the Current singleton property instead
I can't find an example?
so I don't get this annoying warning anymore :)
thanks that does the trick!
Also found some more bugs in Workflow
but they may be resolved already, since you guys have been really busy since my last upgrade
Hi guys, @roblthegreat sorry for the delay. We are working on converting sensenet to be able to work on .net core. Most of the code is converted to netstandard/netcore, but it is not documented yet, because we need to clarify a few things before advertising it - for example patching. And in the meantime we are working on our own service solution that will offer sensenet repositories for developers out of the box, without installing sensenet locally.
@vlad-wallit : the published packages of sensenet contain release build libraries of sensenet which makes it hard to debug the official dlls. If you are willing to compile the code yourself, than it is possible. Get the solution from the github repository (in case of the main backend package this is https://github.com/SenseNet/sensenet), compile it in Debug mode and copy over the result libraries in your local packages (or web bin) folder. Please note that the different sensenet projects generate different dlls (for example SenseNet.Services.dll, SenseNet.ContentRepository.dll), you have to copy them to the appropriate package directory. I know that this is cumbersome and very unusual, but currently there is no easier way. After you have the compiled libraries in place, you have two options: start your application in debug mode and open the sensenet source files you need in the same Visual Studio, or start the app without debugging and use the other visual studio with the sensenet solution open and attach to the application's process.
I've been following the project for a while now and love seeing how active the developer community is behind the project. I noticed you're using Lucene.NET for the indexing, with which I have no knowledge of. I am wondering though, why you chose Lucene.NET and not something like elastic search. Are you trying to keep SenseNet and it's features self contained? IE no external dependencies requiring setup and configuration/administration?
Hi @krptodr, thank you for stopping by :). TLDR: we plan to look into the search service subject mid-term, elastic is one of the candidates, yes :).
Early on we started the project with SQL Server search. However it became clear that it is not flexible enough for us - for example it was not possible (or feasible) to build column indexes for a random combination of fields in a query. We moved to Lucene because it allowed us to use its query API directly (in the application process, without network overhead), which means it was very fast, regardless of the fields that you put into the query.
But this architecture also came with a drawback: we had to maintain indexes locally, on every web node, and notify other nodes every time the index has changed to synchronize indexes. This worked well in an old-school "IIS+NetFramework on a VM" environment, but in a modern, containerized environment would be hard to maintain and automatize this architecture.
And this is how we arrived to the current, service-based search architecture. Currently there is a single, centralized search service, accessed by all the web nodes. This was the first step toward a really scalable search service - because currently it is not possible to scale up this service: Lucene (at least the version we use) does not allow that. The next step would be one of the following options:
Early on we started the project with SQL Server search. However it became clear that it is not flexible enough for us - for example it was not possible (or feasible) to build column indexes for a random combination of fields in a query. We moved to Lucene because it allowed us to use its query API directly (in the application process, without network overhead), which means it was very fast, regardless of the fields that you put into the query.
But this architecture also came with a drawback: we had to maintain indexes locally, on every web node, and notify other nodes every time the index has changed to synchronize indexes. This worked well in an old-school "IIS+NetFramework on a VM" environment, but in a modern, containerized environment would be hard to maintain and automatize this architecture.
And this is how we arrived to the current, service-based search architecture. Currently there is a single, centralized search service, accessed by all the web nodes. This was the first step toward a really scalable search service - because currently it is not possible to scale up this service: Lucene (at least the version we use) does not allow that. The next step would be one of the following options:
- upgrade to the latest Lucene.Net version if it supports sharding/partitioning (I believe it does)
- implement a different search service, based on a similar technology (ElasticSearch, Solr, etc)
The architectural issues we face: - we have a flexible type system which lets users add fields dynamically, while the system is running. Not every search API allows that (without rebuilding the index).
- we need to filter the search results by permissions before they are returned to the web app . It is not an option to let millions of result ids flow through the network every time and filter the results on the web server, it would be too slow.
Let us know if you have more questions or suggestions :).
Hi sensenet Team, while searching for a headless cms i come across this platform and found quite interesting in the concept. We had already evaluated couple of other platforms like contentful and dotcms etc. But none of then matched our requirement. Before proceeding i would like to ask couple of question which may seems childsh.
I had seen content delivery api and content management api in all other platforms, but here it is quite different, i guessed it is retrieved through a query engine. But what if if i need to use cdn for content delivery to get it faster globally? what is the solution for that in sensenet. It will be better if i can know advatnages of query based content retrieval vs API based delivery.
Second point was, regarding events and communication, we are looking to have a real time discusion wall in front end for each workspaces, can i achieve this with sensenet? how do you manage real time communication with sensenet?
Third point is regarding Workflow, we like to automate various process like approval of purchase order, etc in front end with workflow that supports bpmn2. I never saw any details about workflow, do you have plans for implementing workflow engine or connectors for anything like Activity or processmaker or Microsoft Power Automate?
Hi @jamesoliver100 , let me answer you questions here briefly and if it is ok for you, we can continue discussing your needs and questions through email. Feel free to contact us on sales@sensenet.com.
- Comparing query based content retrieval delivery with API based the important difference is that the query based one is far more flexible with the possibility of filtering by path or type, selecting fields, expanding references, etc. To explore the capabilities I would recommend looking at the new documentation at https://docs.sensenet.com/api-docs/basic-concepts. We do not have a CDN solution now but we’re working constantly to make sensenet available to be installed and run on the popular cloud services, which I think would be an answer to this question.
- In sensenet we do not have any solution for real time communication by default, this kind of features can be added with custom development or with integrating a third party solution, but to give you an accurate answer I need further information about your business needs.
- Since sensenet is now moved to .net core, the old workflow solution with Microsoft Workflow Foundation is not available anymore. We’re working now to implement webhooks which we hope to make it available create workflowish things. As I mentioned above we’re eager to hear about your business needs and suggestions, please drop us a mail to sales@sensenet.com.
I have a List of Workspaces I want to query
Each Workspace has 2 groups, Visitors & Members
I want to see only the Workspaces where I am a Member
Both Visitors and Members have See Open Run rights on the Workspace
this through Odata offcourse