Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem removing the Development Toolbar in 3.0.4+. Probably related to a cache problem with configurations. #746

Closed
GoogleCodeExporter opened this issue Mar 25, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Take a fresh Pharo 1.3 image and load Seaside 3.0.4 or newer
2. Try to remove the Development Toolbars as suggested by the Seaside by 
example book:
WAAdmin applicationDefaults
    removeParent: WADevelopmentConfiguration instance
3. Look at the preinstalled Applications in a Webbrowser

What is the expected output? What do you see instead?
All the Development Toolbars should be gone - only some of them are gone, while 
some are still here.

Please provide any additional information below.
This problem occures on Seaside 3.0.4 and newer, but not on 3.0.3.

Paul DeBruicker suggests it might be related to a cache problem introduced with 
http://code.google.com/p/seaside/issues/detail?id=608

I did not check the details, but tried the version before (3.0.3) and after 
(3.0.4) this cache was integrated and this confirms that the problem might in 
fact be related to the cache.

See also the discussion on the MailingList:
http://forum.world.st/I-have-a-problem-with-removing-the-Development-Toolbar-td4
653109.html

Original issue reported on code.google.com by thereluc...@fastmail.fm on 4 Nov 2012 at 1:45

@GoogleCodeExporter
Copy link
Author

Does the following fix the problem:

WAAdmin clearConfigurationCaches

Original comment by philippe...@gmail.com on 8 Sep 2013 at 8:24

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Open the configuration (/config) interface on any application and click 
"Configure" on "Root Decoration Classes" (without accepting or changing 
anything). Then it should be gone.

Original comment by philippe...@gmail.com on 23 Aug 2014 at 5:39

  • Added labels: ****
  • Removed labels: ****

@marschall
Copy link
Contributor

Additionally running the following fixes the issue

WAUserConfiguration allInstancesDo: [ :each |
	each clearSearchContexts ]

@marschall marschall self-assigned this Sep 14, 2018
@marschall marschall added this to the 3.3 milestone Sep 14, 2018
@marschall
Copy link
Contributor

The following methods should be updated to clear all the caches so that they are all a user needs to do

  • WAAdmin disableDevelopmentTools
  • WAAdmin enableDevelopmentTools

marschall added a commit to marschall/Seaside that referenced this issue Sep 14, 2018
marschall added a commit that referenced this issue Sep 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants