Where are configured the folders icons in Thunderbird? - thunderbird

Something happened to my thunderbird profile: now every folder in the folder three pane on the left has the same standard yellow folder icon.
I mean that the special icons for INBOX, Trash etc. are missing.
I've tried to temporarily rename the profile folder, then restarting Thunderbird, now all the special icons are back again.
So the problem appear to be in the profile folder.
I don't want to delete my profile folder cause it contain all my emails.... :-(
any idea?
Edit
I forget to mention the version of thunderbird I'm using: Earlybird v.22.0a2.
As a side note, if I delete the profile and let thunderbird recreate a new one, all the special folders icons (INBOX, Sent Items, Trash etc) on he left pane tree are recreated and showing fine.
But... as I've been asking in my original question, I would like to avoid recreating the whole mail archive, since I've tons of mails...
>>> SOLVED! <<<
Finally I was able to determine the offending plugin!
It was Remove Duplicate Messages (Alternate) v0.3.7
Disabling it and installing Remove Duplicate Messages (original) v0.1.13 from the following link: https://addons.mozilla.org/en-US/thunderbird/addon/remove-duplicate-messages/
solved the problem for me!

In my case 'remove duplicate messages (alternate)', 'toolbar buttons 1.0' and 'color folders 1.0' addons had to be disabled to get the (non-yellow) folder icons back in tb v24. the two latter were running good on tb v23 with 'addon compatibilty check disabled'

Sounds like user-error, rather than a bug.
The left pane lets you pick what part of a profile. It can collapse or grow as you select or deselect; sounds like you de-selected.
BTW, I think this question belongs on Super-User.

Thanks for reporting this behavior! So far, this is the only place where I've seen it mentioned. In my case the bug was appearing in the new Thunderbird v24.0 regular release, and it was caused by the JunQuilla v1.0.2 extension. The developer has released v1.0.3 on the AMO site to address the problem. Currently the "Check for Updates" feature in TB is not finding this version, but you can download it direct from the AMO page for the extension (click the "View other versions" link).
Hope this helps!
(Peter)

I had the same problem (after updating from TB 17 to 24.0.1). It resolved after updating "Compact Header" and "Extra folder columns" add ons.

Related

VSCode remove warnings from problems tab

Im working in a very old Java project (created originally on eclipse) using VSCode and the official plugin for Java.
The project has some folders which are not longer used/valid and I hide them because they dont compile neither. I was able to do this using "files.exclude" in settings.json file.
The thing is I dont want to see those problem in my "Problem" tabs. In addition every time I launch my debugger I get a message saying "Build failed, do you want to continue?" which is really annoying.
So, is it possible to hide those problem which belong to my ignored folders ?
Many many thanks,
This might be helpful to you. v1.41 is adding the ability to filter the Problems pane to not show errors/warnings/info/current file only/hide excluded files. See https://github.com/microsoft/vscode-docs/blob/vnext/release-notes/v1_41.md#problems-panel
Your use-case is exactly the one described in Microsoft/vscode issue 43135, covered by issue 22289
This has been covered by the files.exclude setting that you are using, and the issue 22289 animation shows it does apply to problems too:
Count badge shows total number of problems.
Filtered count is shown in the badge in filter input box.
Filters in Problems view are view only filters. It will only exclude in Problems view.
So... that does not translate to the File Explorer view.
Hence the request:
I like to have a files.problemExclude in settings
Likes other comment in this issue, files.exclude will exclude the entire node_module folder from project explorer, which is not desired.
I just do not want to see any problem in my node_module folder.
That was requested, but closed in vscode issue 52011.
As commented, deleting those folders (kept in version control in a past revision/commit) is the simplest solution for now.

TYPO3 - Error 500 in right panel of Filelist

Friend gave me access to TYPO3 CMS of his page to make some changes and I can not open Filelist.
The left panel with directories is displaying but on the right, a have error 500 message in IE or in Chrome just empty frame.
I did some modifications to that page some time ago and everything was working fine then.
Can anyone help me with that ?
If a folder contains to much files you might get problems opening it in the file list module, as the gathering of all information and maybe creating of preview thumbnails may take longer than is granted to any php process.
If it's only the preview images you might be able to load the folder after some attempts, as sometime all preview images are generated, but as it also can be other delays because of too much files you need to enhace the runtimelimit
or/and you might need to restructure the files and folders.
Be aware that a moving of files with FTP/SSH might break content in the FE as you might invalidate some FAL (sys_file) records so that used files are not found any more. Better: enhance the timeout (temporarily) and move the files in the backend.
in general: if you only got a blank page you disabled all error-messages (which is ok for FE, but will leave you without hint about errors).
As a first start you could take a look in the webserver-error-log.
If you got no clues: enable errormessages in TYPO3 Install Tool (enable debug mode in "Configuration presets")
Ok.
I solved that.
I disabled that extension and then when I looked at maintenance tab on this extension i saw something like "delete LOCAL installation of this ext".
After deleting local installation and enabling system FileList instance, everything is working just fine :)
Thank You for help.

Eclipse Ctrl+Shift+R not showing all files in the project

When i press Ctrl+Shift+R to open the Open Resource Dialog box, the filter box does not show most of the other resource files for example.. jsp, xml etc. it works fine with all the java files.. This is happening for only this particular java project. i have refreshed the project multiple times but still no-go. I have also rebuilt the index for eclipse under workspace/.metadata/.plugins/org.eclipse.jdt.core by deleting the index files but to no avail.
I am using eclipse Kepler version. Any help would be great..
Thanks All. Yes i had closed and opened the project many times. I have also not set any Resource filter exclusions. What i noticed was that opening any of these files for edit would set off an alert saying file was derived and would i like to edit? But on the properties for these file they were not ticked as derived but rather as Archived. So had to manually hunt for the parent folder which was making these files as derived. Also noticed that the Open Resource Dialog box has option for including Resource files "Show Derived Resources"...
This one helped me solve the problem
Eclipse treating all the files in a project as Derived
This is going to sound ridiculous...but maybe this'll help others too: make sure your file search string is correct! You may need to begin it with a wildcard (*).
I lost about 45 minutes on this as the result of user error.
I was looking for some local files named eRCaGuy_PPM_Writer.h and eRCaGuy_PPM_Writer.cpp (from my repo here). So, I pressed Ctrl + Shift + R and searched for ppm_writer, as shown here:
Nothing! It would not find those files! No matter what I did to the files it couldn't seem to find them. I tried all sorts of things. Then, I realized Eclipse doesn't have a fancy fuzzy search like Sublime Text 3, so I simply added an asterisk (*) to the front of the search, and voila! It works perfectly. Since the "PPM_Writer" part of those two file names is NOT at the beginning, I must start the search with a wildcard (*).
Now it works fine, as you can see here:
I've just added a note about this to my personal Eclipse setup and configuration instructions here: https://github.com/ElectricRCAircraftGuy/eRCaGuy_dotfiles/tree/master/eclipse (for my full documentation, see also the PDF and Google Drive links at the top of that page).

Packing an Actionscript (Flash Builder) application for iPhone

Recently I tried to build a flash application in Flash Builder, and I wanted to export it to my iPhone. I have gone through all the required steps in order to certify my application.
Now, with all that done, all that was left to be done is building the ".ipa" file in Flash Builder. Now, this gives the following error:
'Launching TestGame' has encountered a problem.
Error occurred while packaging the application:
NotBefore: Wed Apr 11 18:52:40 CEST 2012
Google didn't give me a decent answer, nor does Adobe's information regarding mobile application development. All I can think off, is that I can't build the application before that date. That's ridiculous, I can't imagine a certain check like that.
I'm pretty sure my ".p12" key file is generated correctly.
Is anyone else familiar with this error? Please, be so kind to guide me in the right direction.
Kind regards,
Matthias.
The error occurs because the compiler didn't find the files under the corresponding directory such as debug-bin or release-bin folder. (explains from: http://forums.adobe.com/thread/893772)
For example, if you are doing a debug-build, and you didn't select the project option: copy non-embeded files to the output folder. And debug-build needs some files such as icons files under the debug-bin folder, and it couldn't find it.
Solution: select project compiling option: the copy non-embeded file to the output folder.
Try again, if still not you will need to try the ADT build to get more details http://help.adobe.com/en_US/air/build/WS901d38e593cd1bac35eb7b4e12cddc5fbbb-8000.html
I suggest compiling from command line. I'd ported an AIR app to iOS and compiled using adt dirrectly (without FB or whatever), and there were more meanful messages then yours. Take a look at the manual on how to build ipa wit adt. The other advise is to check your iPhone node in app.xml (take a look here) and icons.
The "error" was thrown because the certificate wasn't valid yet. It became valid on the date shown above.
You could also fix the manifest file in the iOS developers center.
This problem does come up more often than needed. The error reporting is lacking distinctions but is also difficult to asses since there can be many factors causing this error. If it was one factor or even just a few then it would most likely let you know.
A great way to ensure that the error reporting can do its job and tell you where the problem is is to check your error log. It will tell you at least a few of the places that threw the block.
If you are unable to read those strange glyphs then just ensure that all your resources are being packaged. This does mean a little time of list checking but it is well worth it, for the errors and to get rid of development junk.
The first step in the asset list check is to go through each part of your Assets class (flash builder reference). If you do not have a direct Assets class then you may want to make one and move all of your asset calls to that one class - since it will save you time if this happens again.
Your Assets class is not the same as your Assets folder. Your folder is where the files are stored - i.e. images, bitmaps, sounds, etc. Your Assets class is what categorizes and assigns references to each individual file.
Go through your Assets class to ensure that each of those files exist in the folder as well. Then go to the Project menu (top near Navigate and Search) and select Clean. Either clean all your projects or check the current one. Once this is done you need to click on your Assets Folder (right click or highlight and hit edit or whatever), and select Refresh. This will check that all the files are still there and get rid of/update them.
If none of this throws an error -red X- or other errors then you need to check your project .xml file. This may take you some time to ensure that all of your add on packages and details are correct. Make sure you have the correct:
at the top and it matches your current air release.
Make sure all the filenames, names, ids, version numbers, aspect ratios, fullscreen, visible, icons, extensionIDs, and everything else are not only correct but actually there. Most of these statements should have something written and not be blank. If they are blank find out what to put in.
Ensure that you have the proper icon file extension. If it says assets/icon48.png and the icon48.png is actually in assets/pictures/images/icons/toomanyfilesextensions/whatever/icon48.png
you need to fix that link.
The last thing that you will need to check is when you want to either Release Build or Debug. You need to make sure that all assets are checked and selected.
Go to Project - Properties.
then select ActionScript Build Path.
Click the Native Extensions tab and see if there are any red X's. If there are tap the little arrow beside them and see what the matter it. Add the correct ANE or get rid of it or whatever you need to do.
Then in the same menu go to the left and select ActionScript Build Packaging. A little arrow should be beside that one too. Tap the arrow and it will open to Apple iOS, BlackBerry, Gooogle and whatever else you have (probably nothing more). Select the OS your want to use, lets say Apple, and you will have 4 tabs pop up. Make sure you have the correct certificates selected. If you have none or are confused about this you need to spend some time on Google.
The biggest one for this error is under the Package Contents tab. Most people miss this!
Open the tab and see if anything is not checked. There will 99.99% be something or many of them not checked if you are getting this error. Just check them all and you can figure out what you need and don't need later. Some of them will be listed because you just threw in a bunch of ANEs and .SWFs to have some awesome app. Those add on packages will throw in unnecessary contents into this package. That is fine and don't worry until you want to be picky. Just make sure they are all selected and hit Apply and Ok.
That's it. You should have a working Release Build if you did everything else correct and this error should be easy from now on (but time wasting).
You may get a 'slip' error now, but that is another story. But that is a great sign because you are getting closer to that stupid mistake that we all make: the elusive spelling mistake.

How to change iPhone App name 100%!

Can't seem change the name of my iPhone app 100%.
I followed multiple threads and performed the outlined methods below, but the old name keeps popping back up in Console. I'm concerned that on some deeper level the app's name has not really been changed 100%.
My concern is with the fact that I've made a "Lite" version by starting with a copy of the "Full" version. So I don't want the device to get confused if my customers upgrade and download the full version and the device see two apps with the same "CORE or ROOT" name.
Console continues to output:
2010-07-03 10:56:35.129 *OldAppName* [45672.207] Test Message
I have changed the Product_name, ".app" name, Bundle name, etc... - Where does "Console" get this name, so I can truly change the app's name 100%? I don't want an conflicts with the full version down the road as the apps grown independently in complexity. (i.e. Push Notifications, iAds, and other "APP" specific items)
I have performed the following, but still not getting 100% name change:
I. I have used Xcode, Project, Rename.
II. I have used the suggested answer on stackoverflow thread, Changing iPhone App's Name, to
Go to Targets in Xcode,
"Get Info" on your project's target (your current silly development name),
Search for "Product Name" under "Packaging". Change the value of that what you want the new program name is going to be.
My "Product_Name" field was blank for all builds, I changed it to the new name, but I continue to get the console output referencing the OldAppName.
III. I'm not trying to change the "Bundle Name", those are the same, as this is a Lite Version. And changing this does not change the Console reference name anyway, I tried.
IV. I have deleted the entire "Build" folder several times to assure no legacy issues, but the name still does not change.
I'm currently working on a large copy/paste migration over to a new project to try and fix this completely with a new project, because I would like to get app uploaded to the AppStore asap, but there must be a better way of achieving this.
Where does the "Console" get this name? Does this mean that if my customers' download the full version that on some deeper level the device will get confused-(i.e. NSUserDefaults with the same names, running issue, sandbox issues, etc...)?
The names are not stored in the info.plist, they appear to just be referenced from the target, but when I search through the target, I don't even find the OldAppName, is their an additional storage file for this core information?
I would like to stay in Xcode if possible. I have seen suggestions about using other programs or trying to change the XML directly through text editor, but I don't want to accidentally leave a "Third-Party" application marker or trial that might get rejected by Apple Reviewer's as they seem to be coming down hard on this issue.
Any detailed suggestions??
I had the same problem about a year ago.
I've got really nice & easy solution for your needs. You need to click on the "superview" of blue icon (Project/Targets) and then hit enter to change the name of the project. You can also double click on that field, but you need to do it with quite a long delay between clicks.
This method will change magically name of the project in all important places.
http://i.stack.imgur.com/3f1RD.png
Only Solution that Worked, and it was the one that feared the most and was trying to avoid.
I had to start a new project and painstakingly move all 96 class files (about 27mb of text) over one by one, because dragging the classes over kept giving me an error. I tried dragging over the classes as one large group, but that would not work. A little "re-factoring", rebuilding the .plist info, and setting up the new targets, and it I got it working again. I think that there was some sort of legacy issues that Xcode was getting caught up on.
It is working now under a new project, but there must be a better way.
Have you tried opening all files in your project in a text editor and searching for the old name?
Have you tried creating a new empty project and merely adding your content and code files to this empty project?
I have done these in the past and found they work fine:
http://drjunker.org/2008/04/10/xcode-rename-project-and-application-change-copyright-and-version-number/
http://homepage.mac.com/kelleherk/iblog/C1216817469/E1454445171/index.html
I also Clean All Targets/Builds and rename the Executable after.
I had a problem when there was a localized strings (infoPlist.strings) file in project with "CFBundleDisplayName"="MyOldAppName" in it. Removing this file and renaming target to my NewAppName worked for me.