Aperture 3 Display Bug and Export to Flickr Bug

Has anyone else experienced this issue, and if so what systems do you have and what graphics card are you using?
The issue is the way images are displayed in Aperture. There seems to have been a change in the anti-aliasing between 2 and 3 so than now images with strong highlights display nasty aliasing artefacts and black ringing around highlight edges. It's as if Images are being over-sharpened. Also, when you first move to an Image it displays perfectly fine while it’s loading then when it’s finished it pops into the over sharp aliased version.
I'm having this issue on my iMac 24" running a ATI RadeonHD2600. It seems to only show when the onscreen display is zoomed out to 25% or less. If you go to fullscreen the artefacts disappear on landscape oriented images but remain on portrait. If you zoom in, once you pass a certain zoom factor they disappear.
I have posted some samples of the artefacts here - as well as what they should look like.
http://www.thomas-fitzgerald.net/2010/04/28/aperture-3-is-really-ticking-me-off/
and here
http://theapertureblog.com/2010/03/29/aperture-display-bug/
The bigger issue is that when exporting using the built in fickr tool it uses the same antialiasing and so over sharpens and degrades images the same way.
The problem is not always apparent and it really only shows with images containing high contrast areas, particularly if they clip to white. I would really like to know if this is limited to certain graphics cards as I've talked to someone who has this issue when using the faster gfx card on their macbook pro but not when they turn on the slower one.
If I need to upgrade my mac to make this issue go away then so be it but I'd really like to hear form others who may have seen it?

I have had issues with Aperture's anti-aliasing performance in the Viewer since version 1.5.
To summarize, Aperture's Viewer produces quite jagged edges from Canon RAW files compared to Preview's and Lightroom's renderings of the exact same files. There doesn't seem to be any radical improvements with the 3.x upgrades, and aliasing performance didn't seem to be affected by the updates to Apple's Canon RAW converter (I reprocessed). Images that I had a problem with are still problematic.
I thought that [this thread|http://discussions.apple.com/thread.jspa?threadID=669881&tstart=0] referring to Aperture 1.5 laid out the issues pretty clearly and I was surprised at how little other users were affected by it (or so I infer from the number of responses.)
Until your post I had not looked specifically at Aperture 3.x. I haven't been able to exactly reproduce the issues I had (so many versions ago...) in Aperture 1.5 and it seems the situation has improved a bit.
Aperture still produces a much sharper rendering than Preview, though the aliased edges are not as prominent. To recap from Aperture 1.5:
!http://homepage.mac.com/steve_hoge/.Pictures/AliasedApertureRender.tiff!
And here's what I see in Aperture 3 on the same image:
!http://homepage.mac.com/steve_hoge/.Pictures/aliasedA3.tiff!
Which looks about the same to me on near-horizontal lines, but much better on the high-contrast vertical lines (check upper left corner of the frame).
And today's Preview 5.0.2 rendering of the RAW image is even softer and less contrast-y than back in the day:
!http://homepage.mac.com/steve_hoge/.Pictures/antialiasedPrev.tiff!
-Steve
http://web.mac.com/steve_hoge
http://www.flickr.com/steve_hoge

Similar Messages

[svn:fx-trunk] 10131: Fixes to several effects bugs and one styles-related bug.

Revision: 10131
Author:   [email protected]
Date:     2009-09-10 14:25:42 -0700 (Thu, 10 Sep 2009)
Log Message:
Fixes to several effects bugs and one styles-related bug.
QE notes: Fixes to all filed auto-center feature bugs.
Doc notes: None
Bugs: sdk-22994, sdk-22992, sdk-22990, sdk-21850, sdk-22973
Reviewer: Jason (+Glenn for RadioButton/CheckBox changes, 21850)
Tests run: checkintests, Mustella (transform effects, Slider, DataGrid - all passed last week, prior to skin/test changes)
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-22994
    http://bugs.adobe.com/jira/browse/sdk-22992
    http://bugs.adobe.com/jira/browse/sdk-22990
    http://bugs.adobe.com/jira/browse/sdk-21850
    http://bugs.adobe.com/jira/browse/sdk-22973
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/CheckBox.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/RadioButton.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/effectClasses/SoundEffectInst ance.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/AnimateTransform.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Move.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Move3D.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Rotate.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Rotate3D.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Scale.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Scale3D.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/supportClasses/AnimateTransfor mInstance.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/GraphicEleme nt.as
    flex/sdk/trunk/tools/dependencychecker/frameworkSwcExceptionsList.txt

Stacks and exporting to Flickr

I'm fairly sure this is pilot error, but I can't see where I'm going wrong...first, let me describe what I want to do.
I have a RAW image called "A.NEF" (Nikon D300 RAW). I want to edit it externally in CS5 (could be any editor). When it comes back to Aperture, I now have a file called A.TIF. I really want those to be stacked together - sometimes I shoot multiple images of the same thing (different settings, etc.), so I might have "A", "B", "C", etc. It's really important for me to know that the TIF file came from "A". By the way, I end up having to change the version name for A.TIF because otherwise, it gets posted to Flickr as A.TIF instead of a 'real' name.
So - I stack A.NEF and A.TIF. Great. I have Aperture set up to sync to Flickr, and I created an album called "Aperture Uploads". I highlight A.TIF and drag it into the "Aperture Uploads" album. Now, here is where the crushing disappointment begins... :-((
It ends up dragging the entire stack into the album, not just the one I had highlighted. This means that the original A.NEF and the A.TIF both get uploaded to Flickr. I've also found some odd behavior here - sometimes both of them get uploaded, sometimes it's only one, but there's no consistency.
Can I stack pictures yet still drag a single image from the stack into a Flickr album?

I've had this problem as well, and have basically given up on using the Flickr or Facebook built-in exporting. I know this doesn't answer your question, but I just export to my desktop, then upload those to Flickr, Picassa, Facebook or whatever from there.
It seems when I had Flickr and Facebook photo albums in Aperture, they were constantly being updated when nothing had changed on those pictures, and continued even after I found and unchecked the "Automatically check for new published albums" the preferences.
Good luck!
Jeff

Managing Large Aperture file backup and export

I have a 250GB Aperture library file with 30,000 photos on my Mac Book Pro with a 500GB Solid State driive. I bought a 1TB GoFlex external drive with FireWire 800. I copied the entire 250gb Aperture file to the drive. After 24 hours the file size changed to 180GB? I exported the Masters (full size) from Aperture to the external drive in a separate file that is 60GB as a second backup. I tried to "RELOCATE MASTERS" to the external drive, but it did not reduce the Aperture Libray size by anything. I also exported all of the Versions (full sze) from Aperture to the external drive as a third backup. I am terrified of losing my work which is now all backed up in three forms on a single hard drive. What do I do now?
I must decide whether to use the full Aperture.library on the external drive.. which is HUGE and will only get more bloated.
or import the versions with metadata into a new library but manage previews better.
or what?
Thanks

First, make and confirm two back-ups of your Library and of any Referenced Masters. Your originals and each of your back-up sets should be on separate spindles. Move one of the back-up sets off-site. End of terror: it is now virtually impossible to lose any work you've done up to the point you made the back-ups.
A good set-up to end up with is this:
- Library on SSD
- Masters older than 60 days on external FW800 drive (these will be Referenced Masters; let's call this drive your Referenced Masters Drive).
- - - These constitute a complete Aperture "set".
- Back-up Library _and_ Referenced Masters to _another_ external drive (1st Back-up Set)
- Back-up Library _and_ Referenced Masters to a third external drive (2nd Back-up Set)
- Keep one Back-up Set off-site. Never have all three Sets in the same location.
- Import new files into Library as Managed Masters. Set Previews to be the size of your laptop screen.
- Every 60 days, using a Smart Folder to identify Images with Managed Masters older than 60 days, relocate those Managed Masters to your Referenced Masters external drive
- Back-up regularly
The above is just a template: adjust to suit. (Added:) How you get there will depend on where you are. I didn't untangle your post.
When Images' Masters are off-line (you laptop is not connected to your Referenced Masters drive), you will be able to do all metadata administration, including moving Images, etc. You will not be able to make Adjustments, Export, or Print. (But you can drag the Preview out of Aperture and use it.)
Message was edited by: Kirby Krieger

Lightroom displays files and exports files darker than the original or from Photoshop

Hello all.
I would first like to preface this by stating I am not technically minded, and I know nothing (or very little) of ICC profiles etc.
Though assume someone will attempt to tell me to do something with them in a really technical way which I won't understand, please treat me like a 4 year child in this regard.
I am using Lightroom 5.6 on a Mac running 10.9.4 I have CS6 Photoshop and have a Spyder 3pro calibration device and have linked all of the Adobe programs to the output of the calibration to "hopefully" ensure quality control.
I recently have been scanning analogue film and importing this into Lightroom 5. I have noticed that the file imported always looks darker than the original.
When I have exported from Lightroom them they look like crap.
There are no import additional settings as they are all turned off. I did that when I installed LR.
I have also noticed than whenever I imported a Raw file for some reason the original file would look great for a second then when clicked on would also change to something less appealing. But I digress.
So in attempt to show what is happening. I have created some images to illustrate my problem.
Also it does not matter if I turn the soft proofing on or off.
Lightroom Softproof on
Lightroom Softproof off
Lightroom vs Photoshop Histogram - Very similar
Left: File opened from Lightroom as the Original      Right: Original Photoshop File
Left: File opened from an Export from Lightroom      Right: Original Photoshop File
Any clues as this is very annoying and at the moment makes Lightroom 5 unusable.

Can you put one of your scans somewhere, like www.dropbox.com, and post a public download/share link to it?   I'd like to try one of the scans on my computer, though, to see if it does the same thing. You can crop an original down to something smaller that includes sky and trees like your screenshots show.
I am guessing there is a gamma problem or a profile problem somewhere. What Profile do the scans have embedded in them from the scanner? You can turn on the three Ask checkboxes in your color-settings and see what it says when you open an original in Photoshop.
My guess is that LR is using a default profile that doesn't match what Photoshop is using, but perhaps there is a gamma issue, too.
Have you tried opening one of the originals in the Camera Raw plug-in, perhaps from Bridge or just from PS / File / Open. You may have to set your PS Camera Raw settings to prefer ACR for TIFs. ACR and LR should be about the same in file handling so it'd be interesting to see if that is the case.

Unlink Aperture from Facebook and still keep the albums on Facebook?

Is it possible to unlink Aperture from Facebook and still keep the albums untouched on Facebook?
I really liked the Facebook exporter feature in Aperture until I realized that whenever you deleted a project or photo from the program the changes are reflected in any Facebook album it was associated with. Now I'm concerned about what would happen if something goes amiss with my Aperture Library and would prefer to just manually upload my photos to Facebook from now on. I have seen a few fixes for the same issue in iPhoto but not much about Aperture and don't want to do the wrong this and all my photos disappear from my Facebook.
Thank you in advance for your help.

I do not publish to Facebook, so I cannot try this, but the "Aperture 3 User Manual" say this: See
Publishing Images to Flickr and Facebook
The recommended procedure is to disable your Facebook account in Aperture to unlink it from Facebook, not to delete the albums inside Aperture:
Deleting Flickr and Facebook Albums
You can delete Flickr and Facebook albums in the Aperture library at any time. Keep in mind that deleting a Flickr or Facebook album in Aperture deletes the corresponding Flickr set or Facebook album along with its contents online.
Warning: Deleting Flickr and Facebook albums permanently deletes the corresponding Flickr sets and Facebook albums online. If you want to temporarily remove a Flickr or Facebook account in Aperture, but keep the albums and images as they are in your Flickr or Facebook account online, you can always disable your Flickr or Facebook account in Aperture. For more information about disabling and enabling accounts in Aperture, see Disabling and Enabling MobileMe, Flickr, and Facebook Accounts.
Regards
Léonie

Sharpness APERTURE vs iPHOTO~file exported from Aperture worse than iPhoto

HEY.
i'm recently using Aperture for my Photo Editing work.I found that everything Good and Perfect after fine tune and preview in the Window of Aperture...while Export it to the Jpeg (originaly image import from jpeg file) I found it's a bit loose from what i see in the Window Aperture...means,Loose the Sharpness...whole image getting un-sharp or s'ld i say added gausion blur of feel??
Once i import it(the one exported from Aperture) into iPhoto and Export it (even down size to 800 of diamention) it became Sharp and nice colour tone while compare with the one which Export from Aperture!!!!
Why?
In the Export setting of Aperture i do set the Quality to max 12 and 300dpi even...
Need your hand...thanks!!

WARNING! The sharpness problem is occurring in iPhoto modifications as well! I'm running Tiger and Leopard at the same time on 2 different computers - SAME EXACT SHARPNESS problems. The problem is NOT the OS - it's in the APPLE Photo Aps!

When links are clicked, they do not fully display the NEW page until the mouse is moved.I know it is a current bug, and appears in no other browsers that I know of.

It was pointed out that my links do not function correctly on Firefox on a Windows platform. When links are clicked, they do not fully display the NEW page until the mouse is moved! I have now observed it for myself on my fathers PC running Windows XP on Firefox.My PC is on Windows7
It is the 5 version of Firefox, so I know it is a current bug, and appears in no other browsers that I know of.

Start Firefox in <u>[[Safe Mode]]</u> to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).
* Don't make any changes on the Safe mode start window.
* https://support.mozilla.com/kb/Safe+Mode
If it does work in Safe-mode then disable all extensions and then try to find which is causing it by enabling one at a time until the problem reappears.
* Use "Disable all add-ons" on the [[Safe mode]] start window to disable all extensions.
* Close and restart Firefox after each change via "File > Exit" (Mac: "Firefox > Quit"; Linux: "File > Quit")
In Firefox 4+ you can use one of these to start in <u>[[Safe mode]]</u>:
* Help > Restart with Add-ons Disabled
* Hold down the Shift key while double clicking the Firefox desktop shortcut (Windows)
* https://support.mozilla.com/kb/Troubleshooting+extensions+and+themes

What is going on with all my apple device. Facebook keep displaying users or friend in wrong display picture and today uses my friend picture to display my I D...what is going on. A bug or what?

What is going on with all my apple device. Facebook keep displaying users or friend in wrong display picture and today uses my friend picture to display my I D...what is going on. A bug or what?

IPad and IPhone 4

Solution for Aperture's aspect ratio/export bug?

take an image, then use the crop tool to crop it to a 'perfect' 2x3 or 3x2 aspect ratio.
now export the image.
my case?
Canon 350D images, cropped to 2x3, exported to 'within 750x510' with the purpose of getting an image of 340x510 pixels.
the result? 340x509.
the only way to get a correct export size is to manually change the crop dimensions in the HUD; very inefficient; and sometimes this doesn't work either. rather than getting 340x510, Aperture sometimes skips to 339x510.
it's especially difficult to export images in my favourite mobile size: 174x204, even when using the equivalent 29:34 aspect ratio to crop the image.
any ideas?

found it.
first, I had to extend the length parameter of the Export preset far beyond my goal of 204 pixels and rely on the 174 width and aspect ratio to automatically calculate the final exported length of 204.
next, I had to manually increase the crop length of the image, 1 or 2 pixels at a time, and export each time until Aperture exported my exact required dimensions. it only took 8 tries!!

10 Minor LR3 UI suggestions and some minor UI bugs

Minor UI Enhancements / Adjustments …
Yes I have bigger issues than these but there is enough being said about those already, however I thought it may help to provide feedback on a bunch of more minor things…
1.       Bug? - A weird one here…
The Thumbnail select behaviour is different in folders v’s Smart collections in publish.
In the smart collection – Click a thumb to select it and then shift click another thumb as if to select a range of thumbs… this does not select a range but simply selects the new thumb.   Bizarrely repeat this again and it behaves as expected and repeat again and it behaves badly.   This behaviour alternates between working correctly and incorrectly each time tried.   This strangeness does not occur in a folder.
2.       Enhancement Suggestion - In dimmed develop mode if the cursor is placed just below the histogram then light up the shooting info so can more easily be read OR when dimmed or lights out suggest the “I” key not only toggles the info display but also lights it up whilst the key is still pressed.
3.       Enhancement Suggestion - In “Edit Smart Photo Set” I should not need to press Alt to get the option to have the “hidden” advanced nested selection logic made available.   This is far too powerful a feature to simply hide in this way when “real estate” for another button is not really a problem.   RTFM aside … Why make a secret of such power especially from new users?
4.       Bug? - When editing a text field (In Windows, I don’t know about Mac) in the meta data such as title, key combinations such as Ctrl Shift Left are correctly interpreted as select word left, but Ctrl Left should simply be interpreted as move cursor left within the edit field by a word… not change selected image which is quite irritating.   I.e. when editing a text field all the common edit key combinations should be correctly interpreted and implemented within the field edit, I do not expect any key combination to move thumb selection.
5.       Enhancement Suggestion - Meta data filtering … please make all possible fields available.
6.       Enhancement Suggestion - The “settings” sub-menu on right clicking a photo in develop mode is getting out of hand!   I love the variety and scope of the pre-sets, but surely make it hierarchical to a degree. At least make B&W and Colour pre-sets further submenus.   It is not cool to have a menu which needs to be scrolled because it is actually larger height wise than my large HD screen!
7.       Enhancement Suggestion – The develop controls “light up” as you put the cursor over them, I appreciate dimmed and lights out mode are globally dimming the entire set of panels including the controls… but it would be a nice touch to fully “light up” the controls on cursor over them even when dimmed or lights out.   This would allow easier adjustment with the mouse even in lights out mode.   Again, I appreciate that coding this is more than a simple global dim applied to all the panels.
8.       Bug? - In a Flickr published smart set which has all been published, if I edit the title field of a selected image and enter, the picture thumb is moved to “Modified Photo’s to republish” and is de-selected.   The next thumb is shown as selected, however despite this, the Loupe view and the Meta data panel still show the previous edited image which is no longer selected.   This surely is wrong?
9.       Suggestion .. Remove the serial number displayed in the system info box and put it in a separate box which is not copied when the copy button is pressed.
10.   Suggestion .. It should be possible to copy Smart Collection settings to create a new one from it. Having to export the definition to an external file and re-import it is tedious especially when you use identical smart collections to publish to different destinations.    Even better would be to allow smart collections to inherit their settings from a master smart collection - this would add great power to this facility.
Alan
PS - Windows 7 64bit, Core i7, 8GB

Another minor UI suggestion:
During an adjustment of a B&W mix, let the "Alt" key temporarily display the image in colour again, so that one knows which colours to adjust for certain areas. It would also make it easier to use the TAT, i.e., have a way of knowing where to place it in area of similar B&W shades but different underlying colours,

Bug when exporting table data

The exported columns name are still ordered as the table definition and the data are ordered as the table is diplayed in the explorer. If you change the order of the columns in the explorer and export the data in a csv file by example, the data are putted in a wrong column due to the labeling mismatch.
Table
+column a
+column b
Table data in the explorer
+column b
+column a
Data exported in the csv file
+Title column a
+data column b
+Title column b
+data column a

Sure enough - just tested this with Export > Insert and the column headings are in the displayed order but the data is in the db order. I will log a bug now.
-- Sharon

HELP PLEASE! Export Aperture 1 Library and Import to Aperture 3? Or another way to transfer files WITH changes into new MacBook Pro?

Hi everyone,
I recently purchased a new MacBook pro with Retina display, to better manage Aperture and Photoshop. I took the advice of the genius (and after spending all night messing with permissions, etc.), opted out of using Setup Assistant or Migration Assistant and decided to transfer my files manually (as the two systems weren't merging properly the first time -- it was a giant mess). Long story short, I tried to transfer everything from my previous MacBook (operating on 10.5.8 with Aperture 1), and Aperture 3 couldn't handle it. It was crashing, and crashing so badly that NO button could be activated in the program (I FINALLY got Aperture working by disabling previews, and by moving from a managed library to a referenced library).
I initially dragged and dropped all photos from my previous MacBook to my external, and imported. I obviously lost folders, edit history and any other information that I needed to know what edits had been done on the file. Additionally, any movie that had been imported into Aperture was corrupt (the file was not transferring over correctly). I searched and searched for different methods, and finally found that I could export each project from my original MacBook as a "Library" and consolidate masters, or not, etc. I took the time and did this for each project. When I went to import these into Aperture 3, it said I was not able to because the libraries were from a previous version of Aperture.
Is there any way to bypass this? Or another way to transfer my projects? I understand I won't be able to do this for my entire library... but I'm wondering if there's any way to transfer my changes made, projects and details from Aperture 1 to Aperture 3? (and for those who might pose upgrading my original MacBook as an option, I cannot. It's too old. I think the best I could uprade to is Aperture 2, IF i can update the OS. Though, I definitely don't think I should be forced to do that since I've aleady re-invested in a new computer, AND had to re-buy Aperture for the new one.
Any/all advice is VERY much appreciated, as I really want to move forward and FINALLY start appreciating this program and computer (i.e. my investment) and move forward business wise. Thank you!

Hi Jack,
Thanks for responding (as it seems as though no one else has been able to provide any insight as of yet)! Not sure if you saw my recent post, but the version of Aperture on the 2008 MacBook has been upgraded to 3.1.2 (not sure how; I bought it in 2009, but only have OS X 10.5.8... which apparently can't house 3.1.2 of Aperture, but hey, like many other anomalies i'm encountering, I'm no longer surprised!). I am unable to upgrade it any further, as it warns me that my OS X does not fit the requirements. I exported the projects as libraries; however, like I posted before, apparently these are from too old of a version for the new Aperture (3.3.1) to handle and import.
It's getting to the point where I'd almost pay to upgrade the OS X on my previous MacBook (10.5.8) to something newer in order to THEN update Aperture to a newer version; however, my previous MacBook simply cannot handle this (the specs are awful -- hence my decision to save up and upgrade to the newest MBP with Retina).
I've spent hours upon hours transferring files, libraries as projects, previews, versions, even masters (though, apparently some of them aren't accessible?) with no luck. I've rebuilt the library and reprocessed everything. And this is all after having to return one MBP already since Aperture 3.3.1 is glitch-y as it is, and froze everything for having a "managed library". So, now that I know that I have to deal with a referenced library in Aperture... I just need to actually transfer my previous library to my new one (hopefully WITH adjustments since these are years worth of photos and work).
Again, any help is appreciated. I've lost enough sleep, time, and vision health over this at this point.
Also, I know Migration Assistant is an option, I was told that it wouldn't work properly anyway because of the different operating systems, and the potential for problems.

Java PDK Bugs and Issues

Here are some bugs and issues I've run across using the JPDK that I thought other
developers should be aware of. The following information comes from using JPDK
1.1 with Oracle Portal Version 3.0.6.3.3 Early Adopter on Windows 2000.
1) Do not use a colon character (':') in the String value returned by the method getTitle( Locale l ) in the class Portlet. Registering the provider will appear to succeed, but when you view the Portlet Repository you will get the following error message:
An Unhandled Exception has occurred. ORA-06502: PL/SQL: numeric or value error:
character to number conversion error
Your provider and its portlets will not appear in the Portlet Repository when this error occurs.
Perhaps other characters will cause this error as well.
2) The Provider class method initSession() is supposed to propagate the array of returned Cookies back to the browser. The Cookies are never propagated to the browser. This is a huge road-block for our application and we need to have this problem fixed as there is no workaround.
3) There is a limit to the number of portlets you can have per provider. I initially wrote a provider class that managed 19 portlet classes. However, after registering the provider only 17 portlet classes were loaded by the provider and/or displayed by the Portlet Repository. I had to create a second provider to manage additional portlets. The second provider worked out fine for me because I have 5 portlets that are for "administrator" users only. Moving these portlets left 14 portlets for the first provider to manage.
Note: I don't know if this error occurs using the provider.xml method of implementing a provider and its portlets. My provider and portlets are implemented directly using the Java class API's.
4) Sometimes I will receive the error "Meta data missing for portlet ID=<number>" when a portlet is rendered for the first time. This error does not occur often but when the error happens two conditions are met:
a) The portlet is being rendered for the first time
b) The HTTP and Web Assistant NT services have recently been started.
This error is obviously caused by some timeout but increasing the timeout values
for both the provider and the portlet has no effect. This error may be restricted to the NT platform.
The following notes are not bugs but issues to be aware of:
1) Make sure you have the "sessiontimeout" parameter defined when declaring the initArgs of a servlet in the zone.properties file and you intend to register your provider with a "Login Frequency" of "Once per User Session". For example:
servlet.urlservlet.initArgs=debuglevel=1,sessiontimeout=1800000
If you leave off the session timeout, Oracle Portal will call your provider's initSession() method for every request constantly generating new a session ID.
2) Currently there is no means to check whether a ProviderUser has administrative
privileges. This feature would be extremely helpful for restricting which portlets a user has access to when the provider's getPortlets() method is called.
3) Currently there is no Java API for storing user and global preferences in the
Oracle database. The JPDK provides a PersonalizationManager class but the method
of storing the preferences needs to be implemented by the developer.
The default Personalization Manager persists user preferences as a file
to disk. However, this method opens up security holes and hinders scaleability.
We got around the security and scalability issues by using Oracle's JDBC
driver to persist user and global preferences to custom tables in the underlying Oracle database.
I would appreciate hearing from anyone who has run across the cookie propagation issue and has any further insights.
Thanks...
Dave White
null

David,
Thank you for your feedback on the JPDK. The information you provide helps us understand how customers are using 9iAS
Portal and its development kits. I apologize for the delay in getting back with you. Since you are using the Early Adopters
release, we wanted to test a few of the bugs and issues on the production release of 9iAS Portal.
1) Using a colon character (:) in the String value returned by the method getTitle(Locale l) returned the ORA-06502 error is a
known issue. This issue actually occurs within 9iAS Portal and should be resolved in the first maintenance release scheduled
for 9iAS Portal.
Waiting on reply from Nilay on #1
2) The Provider class method initSession() not propagating the array of returned cookies back to the browser is an issue that we are currently working on. This bug has been fixed for most cases in the first maintenance release. A 100% fix of this issue is still being worked on.
3) The limit to the number of portlets you can have per provider was an issue in the Early Adopter release, but is no longer an issue with 9iAS Portal production. Upgrade to the production release and you should no longer see this problem.
4) The error "Meta data missing for portlet ID=<number>". I have not seen or heard about others receiving this same message. For this error, can you upgrade to the production version and let me know if you still receive this error message. At that time we can check for differences within the configuration.
Not bug, but issues......
1) You have made a good point with the sessiontimeout parameter. The JPDK uses servlet 2.0 APIs which does not provide access to the sessiontimeout. Currently, you will need to specify the sessiontimeout parameter in the zone.properties file.
2) This is true. Currently there is no means to check whether a ProviderUser has administrative privileges. This is on our features list for future enhancements.
3) This is also true. The DefaultPortletPersonalizationManager was created as a default runtime for developers not used to writing portlet code. It allows developers to write portlet code without concentrating on the underlying framework. Once a developer becomes more experienced with the JPDK and portlet environment, we encourage them to create their own
customization manager. This includes changing how the portlet repository is stored or changing how the user customization is
handled and where it is stored. You have no limitations as long as you follow the guidelines of the PortletPersonalizationManager interface.
I hope this information helped. Again, we appreciate and welcome this type of feedback, it helps us not only locate bugs and issues, but also helps prioritize our enhancement list.
Sue

[bug] DB Export - Varchar(n) DEFAULT 'x'

Bug exists in SQL Developer version 1.5.4.MAIN-5940, as well as in old ones.
When exporting DB (Tools -> Database Export, even with default settings), incorrect CREATE TABLE statements can be generated.
After every column of Varchar(n) type, where n can be any number, having DEFAULT values (whether string literals like *'x'* or predefined values like user, a new line marker is added. If it is not the last column, it simply does not look good:
bq. {font:Courier New}{color:#808080}CREATE TABLE "table"{color}{font}{color:#808080} \\ {color}{font:Courier New}{color:#808080}( "COLUMN_A" DATE DEFAULT sysdate,{color}{font}{color:#808080} \\ {color}{font:Courier New}{color:#808080}"COLUMN_B" VARCHAR(255) DEFAULT user{color}{font}{color:#808080} \\ {color}{font:Courier New}{color:#808080},{color}{font}{color:#808080} \\ {color}{font:Courier New}{color:#808080}"COLUMN_C" VARCHAR(255){color}{font}{color:#808080} \\ {color}{font:Courier New}{color:#808080});{color}{font}
But if it is the last one, created statement is incorrect as it contains an empty line like this:
bq. {font:Courier New}{color:#808080} \\ CREATE TABLE "table"{color}{font}{font:Courier New}{color:#808080}\\ ( "COLUMN_A" DATE DEFAULT sysdate,{color}{font}{font:Courier New}{color:#808080}\\ "COLUMN_B" VARCHAR(255) DEFAULT user{color}{font}{color:#808080} \\ {color}{font:Courier New}{color:#808080} \\ );{color}{font}
Edited by: user10659488 on 17-Mar-2009 19:29

There are indeed various problems with exporting. Current workaround is creating a view (temporarily) and exporting form there.
Regards,
K.

Aperture 3 Display Bug and Export to Flickr Bug

Similar Messages

Maybe you are looking for