Is the document tree cached in the Neos CMS backend? I have created two pages under "Home": "Neos CMS" and "Blog" and they are displayed correctly in the main menu of the page preview, but when I click on one of the two page nodes in the document tree, the "Blog" node disappears in the document tree. Only when I click on the "Home" node or the tree refresh button, the "Blog" node temporarily reappears. When flushing the cache via CLI command ./flow flow:cache:flush the node becomes permanently visible.
This behavior is browser independent; normally I use Firefox, just now I used Vivaldi with default settings.
I used the CodeQ Skeleton as the base distribution, but others have confirmed the behavior for the official Neos Base Distribution as well.
I can provide a bash script that builds up a Neos instance for repeating reproduction of this behaviour.
Just for reference here is the link to the Github issue https://github.com/neos/neos-ui/issues/3248
Best would be to reproduce the issue without the Skeleton Package.
I'm not aware of anything in the cache that should influence the document tree. Maybe it's another plugin installed with the Skeleton distribution.
Related
The new version of VSCode 1.75 contains the new function Profiles, which I was waiting for.
It looks like you can install, activate or deactivate extensions in each profile, without affecting the other profiles.
So far I only managed to install, activate or deactivate extensions via the extension manager, or via the view page of the respective extension.
There is this new view that can be displayed via [Settings-Wheel]-[profiles]-[show contents]
There you can find a checkbox for each extension.
Intuitively, one would assume that the extensions for a profile can be either completely switched on or off (install) or at least activated / deactivated.
For me this checkbox has none of the mentioned effects.
The profiles work nevertheless, as said, with an activated profile extensions can be installed and uninstalled, the profiles can then be switched, and a profiles extension states get properly restored when reselected.
However, the view with these checkboxes seems largely pointless to me at the moment.
So my question is: what is their purpose?
Should their purpose be what I suspected, and the feature just isn't "ready" yet?
The checkboxes are for exporting the profile without including undesired configuration options. For example, the "UI State" option will save the currently open menus and submenus as a part of the profile's configuration, which you likely don't really want in most cases.
Notably, when I created a new blank profile and accessed this menu the only field present was the UI State, which implies that if a field is the same as the default configuration it won't be saved to the file.
When you export, you can name the profile and either save it locally as a ".code-profile" file, or upload it directly to GitHub as a gist. The file uses a syntax that I believe is unique, though it's very possible I just don't know it. It would be nice to have a simple JSON schema, but I'm sure the community is going to automate the hell out of this process within a few weeks/days.
I'm pretty sure the purpose of those checkboxes is to select whether or not each extension gets exported as part of the profile. Presumably they are all activated upon importing the profile and installing those profile extensions.
I am using Visual Studio 2019 v16.8.5 and have a single Blazor WASM PWA project in my solution that I recently upgraded to .NET5. In between I got it to run, but lately I cannot get to start it anymore.
The screen says Loading... and that's it.
The console output (Firefox) shows the following error: Microsoft.JSInterop.JSException: Could not find any element matching selector 'app'.
At some point this was running without this issue, but even reverting the solution to an earlier state does not bring any change and I still get a blank screen.
I found a github source saying "just remove builder.RootComponents.Add<App>("app"); from Program Main". If I do this, the error disappears and I just get a blank page saying Loading... with no errors in Console output.
Additional information: I now do a full cache cleanup (cookies and website files) after running the project in Visual Studio to prevent any caching issues.
What am I doing wrong that I can't see any of my pages?
Even after explicitely calling them like https://192.168.188.31:5555/login?
Depending on the template version used to create the initial app, a slightly different HTML is used inside the index.html.
Older version could look like
<app>Loading...</app>
while newer should like
<div id="app">Loading...</div>
In case, the first is still true, the corresponding declaration should be
builder.RootComponents.Add<App>("app");
For the second the line should be
builder.RootComponents.Add<App>("#app");
The second uses the id selector #.
Usually, the index.html is seen as a "static" file and is cached by the browser. So changes, you have done in that file are not reflected immediately. The easiest way to disable the cache is to open the developer tools, go to the Network tab and disable the cache.
I am developing a plugin for moodle. Every time want to review the results of the things I have changed in the code it is necessary to update all plugins. This means I have to open a notification page and click on update. I waste a lot time by doing this. Furthermore, it requires a internet connection to check for updates online.
Is there a way to update plugins that are under development automatically?
UPDATE
Especially changes to the AMD-Files do not become updated. The following steps I have tried:
First try:
change js-file inside AMD folder
[optional] delete minified version of the js-file
run grunt (uglify)
page reload in firefox or chrome
=> no changes visible after page reload in firefox
Second try:
change js-file inside AMD folder
run grunt (uglify)
change version number at version.php
updated plugin at moodle / administration / site administration / notifications
page reload in firefox or chrome
=> changes are visible
Cache was disabled in the browser and inside moodle
You shouldn't need to do any form of update if you have just made changes to your code - make the change, save it, refresh the page.
If you have changed any language strings or CSS or created any new autoloading classes, then Purge the site caches to see the new version.
If debugging is on, you shouldn't need to purge any caches for javascript changes (but you can also set $CFG->jsrev = -1; in config.php, as that sometimes helps).
The only times (during development) when you really need to bump the version number and then visit the notifications page (which doesn't require an internet connection) is if you are adding/removing a capability, changing the database tables in some way or making changes to one of the other files in the 'db/' subfolder (e.g. caches.php, messages.php).
I changed the config.php in the root folder of moodle and added the following lines:
$CFG->cachejs = false;
$CFG->debug = DEBUG_DEVELOPER;
Finally, I saw all changes made to Javascript files stored in mod/my-plugin/amd/src directly on the page without running grunt.
It was not enough to set the debugging options under administration / site administration / development / debugging.
How can I delete the Site Spaces tab as part of the Confluence dashboard? I'm using the Subspace add-on and have no use for that ever growing flat list of spaces.
UPDATE: I'm using the latest Confluence version 5.x what ever exactly that is. The Subspace add-on offers a hierarchical view of all Spaces so I don't need the default flat view that doesn't scale well and bloats the Confluence Dashboard page.
This is how I would edit the dashboard macros in Confluence version 4.3.something, I think it's more or less the exact same process in version 5:
First, access the site administration page by going to "Edit" -> "Administration" -> "Site Administration"
Once you're on the site administration page, look for the "Add-ons" section of the left hand menu. There should be a "Manage Add-ons" link under that section, click it.
Now you'll want to scroll down to the "System Plugins" section. You'll need to click the "Show System Plugins" link in order to have these add-ons displayed. These add-ons are not displayed automatically because changing them can seriously impact the functionality of certain parts of confluence. Be careful here to not change anything you didn't intend to, and make sure you can undo any changes you do intend to make. I would recommend having the dashboard page open in another browser window or tab so you can refresh it without leaving the "Manage Add-ons" page. This way, if you accidentally change or remove something fatal, you can revert any changes without a great deal of trouble.
Once the system plugins list is displayed, scroll down until you see the "Dashboard Macros" item. Click that, and then, depending on your settings, you will either have to choose "Manage Plugin Modules" or you will simply have to expand a list of modules which are enabled. From here, you can find the modules you want to disable and do so. For instance, you could simply disable the "Popular Tab" module to remove that from the updates list, or you could choose the "spaces-list" module to remove the long list of all site spaces. Once you've made the changes you want, be sure to refresh the dashboard page to check the impact you've had before closing the administration page. When you're finished, drop administration access to avoid unintentionally breaking something down the road.
Here's a link to some general information about customising the dashboard in 4.3:
https://confluence.atlassian.com/display/CONF43/Customising+the+Dashboard
and here's a link to the same basic info for version 5:
https://confluence.atlassian.com/display/DOC/Customising+the+Confluence+Dashboard
I hope that helps.
The local save feature of the Chrome Dev tools Sources tab is very powerful.
However, I can't completely tell what kind of changes actually hold.
What changes are actually activated?
Ctrl-S applies your changes into v8.
So the the dynamic page behavior will work differently according to the changed code.
The star symbol in the file title indicates that the recent changes in the file haven't been sent to v8.
You have to save the changed file to the place where the web server gets it if you want to see the changes after reloading the page. You could do that with help of context menu.