Multiple open projects issues

I have had to stop having more than 1 Pinegrow project open at a time as it has been causing me countless issues / frustrations. I have 4 projects that are largely identical bar the text content and the images - i don’t know if it is this similarity between projects that is causing the issue or if there is a general issue.

There are 2 main issues that I see, the second of which only seems to happen when projects are opened in the same window.

  1. When i open a second project the styling gets completely broken as the link to the tailwind css file (in tailwind_theme) shifts to try and css link to the originally open project’s version of that file (i.e. by prepending ../Other%20project/ to tailwind_theme/tailwind.css).
  2. When i select any element in the tree, the properties panel for that element does not update to show details for the selected item. That panel instead seems to be locked to the selected item in the originally opened project.

****

If i open any of the projects individually things work fine so that is what I have been doing but as the projects are similar I often want to copy elements / css between them and so having multiple open at once would be far preferable.

Is this the place to raise bug reports? Has this been logged / investigated?

i see pinegrow 9.2 has been released. New features look good but how can we determine which of the many bugs that are in the app have been fixed? Is there a proper list somewhere as the release notes aren’t informative in the slightest.

Email them direct to support is the best option.

@oddballs Since you reuse elements across projects, instead of opening multiple projects (which seems to be causing issues for you right now and whose support report will be reviewed in the coming days), have you thought about creating component libraries you could reuse much more efficiently between projects?

This is a far more effective feature for the kind of operations you describe, and it could be an interesting workaround.

I can take a look at that approach - can the component be a shared file (i.e. my custom CSS file)?

The issue is around the reference to the custom CSS file in each project as it gets changed by Pinegrow when multiple projects are opened to point at the file in a different project.

Take a look at our comprehensive documentation on this topic :slight_smile:
Just so you know, the documentation uses Pinegrow’s flexible mode interface.