Unable to Add HTML Elements

[David Althausen]

I just started using Structr this week and am not a programmer but am familiar with graph theory and see a lot of potential to manage manufacturing through the use of Struct.

Running through the tutorials I ran into a problem when using Add Page. Right clicking on the Div would not allow me to add any HTML element. Furthermore, the right click dialogue would not even appear. Later I was able to add elements using the HTML Palette. After using the Palette, I was then able to right click and add elements later even on a new page.

Some information on my setup:

OS: Windows 10 Pro

Browser: Chrome Version 88.0.4324.190

Installation Method: MSI Installer

Screenshot of problem: Unable to provide since a right click did not generate a dialogue box

[David Althausen]

Sorry forgot to add that I am running Struct version 3.5.1, Community Edition.

[Kai Schwaiger]

Hello David,

thank you for the detailed problem report!

I see the problem: There was a bug in the context menu that has been fixed in more recent versions.

After creating the first Page, you have to reload the Page once. Afterwards the context menu works as intended.

This only happens right after installation for the first time a Page is created.

As I said, this has been fixed in more recent stable releases, but we moved a bit away from dedicated MSI Installers in favor of Docker.

For our next big release - coming soon - there will be an MSI Installer again, though

You could run the latest release version 3.6.3 like this:

docker run --env=AGREE_TO_STRUCTR_PRIVACY_POLICY=yes -ti -p 0.0.0.0:8082:8082 structr/structr:3.6.3

Does that work for you?

Best regards,

Kai

https://structr.com
Kai Schwaiger COO kai.sc...@structr.com Festnetz +49 69 / 3487287-80 Mobil +49 177 / 48 16 204
Structr GmbH Hanauer Landstraße 291a 60314 Frankfurt am Main Deutschland / Germany	Geschäftsführer: Axel Morgner Sitz der Ges.: Frankfurt a. M. HR: AG Frankfurt a. M. HRB 92262 Umsatzsteuer-ID: DE 279486092

-- 
You received this message because you are subscribed to the Google Groups "structr" group.
To unsubscribe from this group and stop receiving emails from it, send an email to structr+u...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/structr/a0d66a5a-25f1-4ff1-9661-2da049e3d77en%40googlegroups.com.

[David Althausen]

Hi Kai,

Thanks for the info. I was able to get Structr up and running with Docker. However, will it run with a community license? The Structr container now exits and based on the log (attached) it seems that it exits because it is not authorized to connect with Neo4j??? I have been using Docker Compose to launch the service via the YML file on GitHub. It originally launched 4.0 Snapshot and this evening I changed the reference in the YML file to 3.6.3. The attached log reflects issues since making the change to the YML file.

David

[Kai Schwaiger]

Hi David,

Could you share your YML file so I can have a look at it?

About the license: The evaluation license i valid for to weeks, that is why you see the log output that the evaluation period ended March 17th.

If you download Structr again via the website you’ll receive a new license valid for another two weeks.

Best regards,

Kai

https://structr.com
Kai Schwaiger COO kai.sc...@structr.com Festnetz +49 69 / 3487287-80 Mobil +49 177 / 48 16 204
Structr GmbH Hanauer Landstraße 291a 60314 Frankfurt am Main Deutschland / Germany	Geschäftsführer: Axel Morgner Sitz der Ges.: Frankfurt a. M. HR: AG Frankfurt a. M. HRB 92262 Umsatzsteuer-ID: DE 279486092

To view this discussion on the web, visit https://groups.google.com/d/msgid/structr/3706e0e2-01d9-4762-a353-172e64d80e9bn%40googlegroups.com.
<Docker-compose log.txt>

[David Althausen]

YML file is pasted below.

version: '3.3'

services:  

  neo4j:

    image: neo4j:3.5.25

    # Uncomment to give host access to the service container

    # ports:

    #  - "7474:7474"

    #  - "7473:7473"

    #  - "7687:7687"

    # For swarm mode deployment only.

    deploy:

      resources:

        limits:

          cpus: '2'

          memory: 4g

        reservations:

          cpus: '1'

          memory: 1g

    # Add volumes for data retention

    volumes:

      # folders

      - ./volumes/neo4j-database:/data

      - ./volumes/neo4j-logs:/logs

    # Put service networks so Structr and Neo4j can communicate

    networks:

      database:

        aliases:

          - neo4j

  structr:

    image: structr/structr:3.6.3

    depends_on:

      - neo4j

    ports:

     - "8082:8082"

    environment:

      - AGREE_TO_STRUCTR_PRIVACY_POLICY=yes

    # For swarm mode deployment only.

    # If changes are made here, then it's also a good idea to make the adjustments to the 

    # memory.conf file which contains the Java runtime configuration for Structr.

    deploy:

      resources:

        limits:

          cpus: '2'

          memory: 4g

        reservations:

          cpus: '1'

          memory: 1g

    # Add volumes for data retention

    volumes:

      

      # folders

      - ./volumes/structr-files:/var/lib/structr/files

      - ./volumes/structr-repository:/var/lib/structr/repository

      - ./volumes/structr-logs:/var/lib/structr/logs

      # config files for initial configuration of Structr

      - ./structr/structr.conf:/var/lib/structr/structr.conf

      - ./structr/license.key:/var/lib/structr/license.key

      - ./structr/memory.config:/var/lib/structr/bin/memory.config

      # Put service into network so Structr and Neo4j can communicate

    networks:

      database:

volumes:

  structr-files:

  structr-repository:

  structr-logs:

  neo4j-database:

  neo4j-logs:

networks:

  database:

[Lukas Reich]

Hi David,

I had a look at this problem and was able to reproduce it, thanks for bringing this to our attention!

By default, Neo4j requires authentication and expects the default credentials neo4j/neo4. However, default credentials have to be changed upon first login, which Structr versions < 4.0 can't do.

To fix this, the initial Neo4j credentials can be set by adding the environment variable 'NEO4J_AUTH=neo4j/structr' to the yaml file. I added the variable to the Neo4j docker service as a comment in our repository, so you can have look there or you can add these line to your yaml file:
...

services:  
  neo4j:
    image: neo4j:3.5.25

    environment:
     - NEO4J_AUTH=neo4j/structr
...

I hope this fixes the problem for you aswell.

Best,

Lukas

[David Althausen]

Hi Lukas,

I'm not sure why this didn't work. But before that, I think the spacing on the GitHub file isn't correct. I deleted it out and replaced it with the text you supplied above and that allowed docker-compose to run. The Docker log is attached and the yml file is pasted below:

version: '3.3'

services:  

  neo4j:

    image: neo4j:3.5.25

    environment:

     - NEO4J_AUTH=neo4j/structr

[Kai Schwaiger]

Hello David,

It’s Kai again with some input :)

I think I know what’s going on. Even though the password for the user “neo4j” has now been changed, that user

Is still blocked.

I assume you never used this setup so we can safely reset to the initial state of the database, correct?

If so, we can do the following:

1. Run “docker-compose down”

2. Delete the complete “volumes” directory. (So in my case “rm -rf volumes”)

3. Run "docker-compose --compatibility up -d"

That should give us a fresh start and the connection should establish fine.

I watched the initialisation using "docker-compose logs -f” and everything ran fine.

The only changes from the default repository in my case are the following. I think yours should look identical:

Hope that helps!

Best,

Kai

https://structr.com
Kai Schwaiger COO kai.sc...@structr.com Festnetz +49 69 / 3487287-80 Mobil +49 177 / 48 16 204
Structr GmbH Hanauer Landstraße 291a 60314 Frankfurt am Main Deutschland / Germany	Geschäftsführer: Axel Morgner Sitz der Ges.: Frankfurt a. M. HR: AG Frankfurt a. M. HRB 92262 Umsatzsteuer-ID: DE 279486092

-- 
You received this message because you are subscribed to the Google Groups "structr" group.
To unsubscribe from this group and stop receiving emails from it, send an email to structr+u...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/structr/97bcbd4b-bda6-474a-aba1-54813ae5543an%40googlegroups.com.
<Docker-compose log 210319.txt>

[David Althausen]

Hi Kai,

Deleting the Volumes directory was the solution. I am up and running now.

Thanks for the help!

David