Stacks, versions, links, albums, projects, grief.

I'm having some confusion. I want two versions, one cropped, one not cropped. I want one album to have all the not cropped versions and another album to have the cropped versions.
If I stack the versions, then the stack exists in both places. Changing the head of the stack in one album or project changes it in all the others. This would seem to be a bug according the "getting started" pg 76, "the version set pick is specific to the album it's in".
What I really want to do is take a set of shots, dup'em all, and crop them all to a particular aspect ration. Then do it again for a different aspect. I'm happy with cropping them manually, but I can't figure out how to dup'em all short of doing something dreadfully dreary like copying them one at a time, breaking the version set, manually flagging one of the version set one way and the other another so that I can search sort them into different albums.
Is there a better way to manage this? Is there any way to get aperture to actually "create new versions when making adjustments"?

Richard,
I would do the following (quite straightforward):
- Take a fist pass at cropping; that will create
"Version 2" for each image
No, this simply edits the first version, the one with no "version X" after it.
- take a second pass at cropping; set "new version
from master" for that run
This does the same thing, whether "create new version on adjustment" is set or not. So again, the first version is changed.
- ... Keep going like that....
Then run a query where you search in the Query-HUD
for all versions that end with "version 2" or
"version 3" etc. Just go ino the HUD, click on "other
metadata" and set Version ends with..."Version 2" for
example.
Done.
Does that work for you?
Nope. The only time I've ever seen a "version 2" was when I manually duplicated a version. How else can you create them?

Similar Messages

Missing Stack/Version Set opt. when "move to removable" with album

I'm using windows XP and I occasionally move pictures to a DVD and retain thumbnails for organization. If I use picture that DO NOT belong to an album and do a "copy/move to removable disk" I get three options (move, stacks, versions). If I use a picture that IS IN AN ALBUM and do a "copy/move to removable disk" I only get the single move option, the include stacks and versions set aren't grayed out, they simply aren't there. I'm working with photoshop elements 6 and have got the same results with photoshop elements 7.
The work around I have is to move all unsorted pictures into an album and REMOVE the pictures from the albums I want from that album into the unsorted/unassigned. This is really annoying because I'm trying to organize pictures with albums and backup to dvd (2) for safe keeping and not cluttering up the computer with pictures.
Does anyone else experience this? Anybody have a solution? I want a simple way to move to DVD and only retain linked thumbnail on computer.

Tony,
I dont think the solution is written down anywhere its just one of those things you figure out after using the Organizer for a really long time.
PSE albums have annoying behavior with respect to stacks and version sets. If you put one photo from a stack/set into an album, the entire stack/set gets placed in the album, and if you delete one photo in a stack/set from the album, all the photos from the stack/set get removed. The behavior you discovered you can only move the top photo in a stack/set is strangely inconsistent, but not surprising. Adobe has introduced a number of sloppily designed features in 6 and 7.

Are Versions in Albums identical to Versions in Projects?

I'm reading the manual but not finding an answer to something I don't understand.
I am trying to clean up a database that has too many Versions (as I understand the terminilogy) in a number of different Projects and a number of different Albums. This means it is possible that I have an Image of a Master (a "Version") in "Project 1" and "Project 2" but /also/ in "Album 1" and "Album 2".
What I am trying to understand is how to construct a good methodology for getting rid of these duplicates and if in fact all FOUR of these are basically identical.
A. Basically what I am wondering is if I can delete all the Versions in all my ALBUMS - in bulk - and be assured that I am not deleting Masters if I don't get a warning prompt.
B. Or if it makes more sense to try and /move/ all the Versions in all my Albums to the same Project the other Versions reside and to then delete these duplicate Versions one by one. In this case, I also need to know if I can basically delete three images in bulk and not worry about deleting a Master (provided I get no warning) provided I have another Version of this image in the Project (or database).
Thanks for any advice on this. The warning prompt seems to be rather vague about this and I don't see it treated in the Aperture Help.
TIA.

Hi Ernie.
Thanks. Perhaps we can just have an exchange of information here?
I think the issue I was trying to determine is somewhat tied to why Aperture doesn't warn me that I am deleting a Master. It is rather easy to Delete a Version in an Album without thinking twice - or having any way of knowing - that you have just deleted the Version in the Project that it originated from. I mean, Albums seem like little floppy little things that no one worries about much because you always have your Project as a larger container.
Also, while it is possible to Remove a Version from an Album - if you are trying to clean up Albums in bulk, or many at a time, you are likely to Delete the Album. /Deleting/ the Album /sounds/ like it could be also deleting your Versions in your Project which one may likely not want to do.
Furthermore, since my Album may not only have Versions from multiple Projects, I may also have multiple Versions of the same - hmmm what is the correct way to say this? What do I say? I say that an Album may have Versions from multiple Projects but it may also have Versions that have multiple Versions in multiple Albums! Lord is there a more fundamental way to say this?? Anyway, what I am trying to say is that it is not so easy to "line check" in Aperture by following something out logically.
After all, I may just want to delete an Album without deleting my Master or I may just want to delete multiple Versions in various Albums without deleting my Master or I may even just want to clean up straight-up-duplicates of the /same/ image which are showing up as identical looking Versions that reference different Masters. None of this is straightforward to even describe let alone figure out.
The easy way to clear this up IMHO is for Aperture to give you a prompt that you are deleting the Version in your Project when you Delete a Version in a Album. Why it cannot give you a warning that you are deleting a Master (i.e. the last Version in a Project associated with it) is mind boggling to me.
The other nice thing that it /could/ show me is to give me some kind of easy way to /see/ that the Version I am looking at in my Project has a VERSION IN AN ALBUM. I have done this myself manually by coloring every single version in every single album that I need to retain - so that I don't accidentally delete a duplicated Version that has a Version in an Album - but it would be much more straighforward if it just did this with an optiion. It could even tell me /which/ Album or Albums it was referenced from.
ALSO. The documentation in Aperture specifically states that you have Masters and Versions in a Project. From everything I can tell a Master is effectively the last remaining version so it acts as this sort of ghostly apparition which no one sees, and only means something when you delete the last version.
Anwyay, I know it may sound like I am arguing with you but I am not. I am just trying to explain what I understand about the software and in the process test my fundamentals. I mean, it is all well and good for me to do this in front of my computer by making tests and such but I find it great to have an exchange of information where there is at least a remote possibility that we both learn something.
Anyway, if you got this far would you mind telling me where I am in error in the above or if you see me thinking incorrectly about something? You've been a great help as have others and I feel like I can flap a little harder now and at least get a little movement.
Cheers!

AppleScript Bug: Duplicating stacked images to albums

for anyone else using AppleScript, I encountered this bug a couple of nights ago. I've reported it to Apple.
14-Feb-2009 02:14 AM Gregory Charles Rivers:
Summary:
The Aperture/AppleScript "Duplicate" command when used to add stacked images to albums does not work as expected.
(1) when stacked images are successfully added to the target album, they are added as masters rather than simple album items.
(2) if the source project is not selected in the Inspector, stacked images will not be added to the target album.
(3) "Duplicate" is not a suitable command for adding objects to albums and confuses scriptors. an additional "Add" or "Assign" command should be created expressly for this purpose.
Steps to Reproduce:
* begin of steps to reproduce *
PROBLEM #1
1. [APERTURE] import 3 masters into a new project called "Gregory"
2. [SCRIPT] in a script editor, get the new project's ID:
id of every project whose name is "Gregory"
-> "UkRHKvb/RfmZ8H+Jn/pxRA"
3. [SCRIPT] get a list of the images in the new project:
every image version of project id "UkRHKvb/RfmZ8H+Jn/pxRA"
-> a list of 3 objects
4. [APERTURE] create two albums within the project:
-> "Album 1" and "Album 2"
5. [APERTURE] stack the first two images.
6. [SCRIPT] add only the first image to "Album 1"
copy every image version of project id "UkRHKvb/RfmZ8H+Jn/pxRA" to theImages
duplicate theImages's first item to album "Album 1" of project id "UkRHKvb/RfmZ8H+Jn/pxRA"
-> the stack that image 1 is a member of, is added to the album, but it's not a normal 'linked' album item.
7. [APERTURE] delete the image from "Album 1" by selecting the image and pressing "Delete" on the keyboard.
-> a warning is sounded but nothing happens. with normal album images, they're simply removed from the album.
-> "Remove from album" is greyed out in the Images menu.
8. [APERTURE] select the first image of the stack within the album and press Command-Delete.
-> a dialog is presented confirming that the images inside the album are masters.
confirm.
-> the image is removed from the album, and from the project!
9. [APERTURE] select the remaining image and press Delete.
-> the image is removed from the album without affecting the master as would normally be expected.
(the work-around for removing 'masters' from the album is to unstack them after which they become 'normal' album items again.)
PROBLEM #2
10. [APERTURE] import the first master again, back into the same "Gregory" project.
-> we now have 3 masters in the project.
11. [APERTURE] stack the first two images.
12. [APERTURE] within project "Gregory", select "Album 2".
13. [SCRIPT] add all 3 images to "Album 1" (while "Album 2" is still selected within Aperture).
copy every image version of project id "UkRHKvb/RfmZ8H+Jn/pxRA" to theImages
repeat with i in theImages
duplicate i to album "Album 1" of project id "UkRHKvb/RfmZ8H+Jn/pxRA"
end repeat
-> only the unstacked image is added to the album.
14. [APERTURE] select the project "Gregory".
15. [SCRIPT] run the script again.
copy every image version of project id "UkRHKvb/RfmZ8H+Jn/pxRA" to theImages
repeat with i in theImages
duplicate i to album "Album 1" of subfolder "nested" of project id "UkRHKvb/RfmZ8H+Jn/pxRA"
end repeat
-> all of the images are added to the album.
-> the stacked images are still 'masters' rather than simply album items.
PROBLEM #3
the "Duplicate" command should be used for adding images as links to objects such as albums. the use of the "Duplicate" term for this action leads to confusion. an additional "Add" or "Assign" command should be created for this specific purpose.
* end of steps to reproduce *
Expected Results:
whether stacked or not, images added to albums should be simple linked items, not masters, and which when deleted by pressing Delete simply disappear from the album without affecting the true masters.
Actual Results:
(1) stacked images added to albums are added as masters instead of linked items.
(2) stacked images cannot be added to albums if their containing projects are not selected in the Projects inspector.
(3) the use of the term "Duplicate" when applied to adding items to albums is confusing because the images aren't actually duplicated.
Regression:
Unstack all images before running any script that adds stacked images to albums.

I have noticed behavior with drag-and-drop working anomalously different for me than as reported by others. It has not yet been problematic, but definitely anomalous.
It sounds like the Aperture team should forget features improvements for a while and focus on stability.
-Allen

Versions in my Projects that are Masters

When I import an image into Aperture and it goes into a Project, if I delete this Image by going to "Delete Version" this deletes the Version and the "Master" (wherever /it/ is) without a warning is that right? I ask in part because the Aperture Documentation states specifically that there are both "Masters" and "Versions" in Projects in a managed images database and this is uber confusing.
Also, if I import an image into Aperture and it goes into a Project, and then I create an Album and drag and drop this "Version" into the Album - so that there is a "Version" in the Album - if I go to "Delete Version" from within the Album, Aperture will delete the Version in the Album *AND* it will delete the "Version" in the Project without a warning, is that right?
Both of these appear to be the case no matter how many "Versions" of the image you have in a Project or have copied to an Album.
I guess I have found it terribly confusing for Aperture to be /then/ giving me a Warning Dialog that says I am deleting a "Master" that may be referenced from other Albums. Because I personally am MORE concerned with deleting the /original images/ that I have imported which I can do from within Projects or from within Albums without any alert.
Am I missing something here?
THANKS.

Yeah. This just seems very weird to me.
I mean, I /really/ care about deleting my Masters and I get no warning about this whatsoever in any cases (deleting from a Project or Deleting a Version from an Album). I could be deleting a Version in an Album and accidentally think that I have another Version in another Album and poof away goes the Master when this is not what I thought I was doing.
And the warning that /does/ come when you are going to delete a Master from within a Project /sounds/ like it is about deleting a Master - - that by the way /may/ or that may /not/ be linked to an Album. When in reality it is simply telling you the Version in the Album is going away. Then if you delete a Master that /doesn't/ have one of those links to a Version in an Album you get /no/ warning. Yikes.
I think they need to clear up the language on the prompt IMHO because right now it is uber confusing. And really there should be two:
I: "You are deleting a Version in an Album that will also delete the Version which is a Master in a Project".
II: "You are deleting a Master from a Project which will also delete a Version that is contained in an Album".
- Jon

Keeping different versions in separate projects

When I duplicate a version or make a new one from a master it appears in the same project. After I have made some changes to the duplicate and want to safe this changed version in another project Aperture automatically moves the original with it.
If I keep them in the original project it shows original and altered versions all together. I want to avoid this because I want to keep the changed versions in a separate project.
Working with albums doesn't seem to work because changes made when working on an image in an album are automatically visible in the image in the project
Any help is appreciated,
Rob

Album Picks are the feature you are missing.
Versions are simply text-instruction-based variations on the Master. They are small -- so small that you should make as many as you need. Aperture by default Stacks Versions in what it calls, with uncharacteristic directness, Version Stacks. Each Stack in a Project has a Pick. The Pick is the Image that shows when the Stack is collapsed.
Stacks in Albums have Picks as well. These are Album Picks. The Album Pick need not be the pick that shows when the Stack is collapsed in its Project.
To do what you want, create new Versions of Images, put them in a newly created Album, make each of them your Album Pick (this can be done automatically), collapse your Stacks, and then make your Adjustments. You'll have a Stack in your Project with the original imported file showing as the Stack Pick, and in each album you'll have each of your adjusted Versions showing as the Album Pick.
The Stack stays together. The Picks are container-specific.
RWBoyer has excellent information re: Stacks and Picks. Search the forum, and take a look at his Web site.
If that doesn't help -- keep asking.

How do I add an individual photo from a stack to an album?

I'm trying to add a photo from a stack to an album. However, even if I un-stack the photos in the parent folder & copy a single photo into the album when I then re-stack the original photos they all appear in the album too. Is there a way around this or do I just have to leave all my pictures un-stacked?
Thanks for any help you can give.

photojester wrote:
I'm trying to add a photo from a stack to an album. However, even if I un-stack the photos in the parent folder & copy a single photo into the album when I then re-stack the original photos they all appear in the album too. Is there a way around this or do I just have to leave all my pictures un-stacked?
Thanks for any help you can give.
You can't include an item from a stack in an album. What you include in the album, is the link to the top level member of the stack. If you change the order of files in the stack, that is reflected in the album.
Best solution in my opinion : temporarily expand the stack, select the wanted item and export it somewhere. Then 'import' it in the organizer and put it in your album.

How do I copy only the flagged image in a stack to an album?

Within a project containing many stacks, I want to make an album showing only flagged images from some of these stacks. But when I try to do this, I end up with the stacks in the new album - which is not what I want.
For example, from a small gathering I have 94 photos in 24 stacks. (Among other things, I auto-bracket.) The correct image is the "pick" in each stack. I flagged 8 photos and uploaded them to a Picasa Web Album, for people to see. I want to make an album inside the project showing only the photos I uploaded, but I have not found how to do this.
I can view the 8 flagged photos by filtering, and though each has a badge showing the number of photos in its stack, the remaining photos do not appear if I click on the badge or press Shift-K or select Open/Close Stack: all that happens is that the badge toggles between the number of images in the stack ("x") and "1 of x" - say, between "4" and "1 of 4", if there are 4 images in that stack.
But when I put a flagged image into an album, I get its whole stack. It does not matter whether I drag it or choose New > Album and click the "Add selected items to new album."
This seems like such an obvious task that I feel I must be missing something.
Any help?

Just to expand on Frank's answer: that's how Aperture works. Stacks travel together. You will see the same behavior regarding filtering in the Album that you see in the Project. (Album is a container. As with a Project, you can filter the Album container to show only items that meet your filter criteria, but the contents of the container don't change by being filtered.)
This is why Album picks are so useful. In Projects, the Stack Pick is the left-most Image in the Stack, and is the Image that shows when the Stack is minimized. In Albums, you can specify an Album Pick. (The default Pick is the Stack Pick.) When a Stack in an Album is collapsed, the Album Pick is the Image that shows on top.
Added the following paragraph:
So you could have a Project with Stacks of bracketed exposures (an excellent use of Stacks), you could make the best of these the Pick, and then you could make an Album showing, say, the second best ones by putting them in an Album and designating the second-best Images as the Album Pick of each Stack.
You should have no trouble creating an Album of your selected Images (in this case, you are selecting by "is flagged"). With Stacks collapsed, you should see what you seem to want, which is a group of the Images you selected to be in the Album.
denke wrote:
I want to make an album inside the project showing only the photos I uploaded, but I have not found how to do this.
That the rest of the Images in the Stack are there shouldn't be a concern. Why is it?
Message was edited by: Kirby Krieger

"Library" Projects vs "Projects & Albums" Projects

Hello all,
I have been using Aperture for about three years. I have Aperture 3 on three different Macs.
Prevously I have been using Windows XP and have been storing photos in directories on the hard drive the old fashioned way.
I have some questions about the storage structure of Aperture and I cannot find the answer in the Manual nor online.
Here we go.
1. When I import photo's into Aperture, it creates a "Project" both under "Library" Projects and under "Projects & Albums."
Q: If I delete a project under "Library" do the photo's contained in that project get deleted from Aperture's Library?
Q: If I delete a project under "Projects & Albums" do the photo's contained in that project get deleted from Aperture's Library?
2. I have been a user of Mobile Me gallery since it came out, even before I bought Aperture. I have synced the Mobile Me galleries with my copy of Aperture 3 on each of the mac's so I have redundant copies. I understand that Aperture will automatically sync changed photos so I am pretty sure all the image files for each mobile me gallery now exists on my hard drives.
Q: As Mobile Me Gallery will not longer be supported in June, if I delete a Moble Me Gallery via Aperture, will the images in my Aperture Library still be there?
I know this question seems odd, but the manual is not really clear on this issue.
3. While I am here asking the pro's this is a question I think I have figured out.
Q: The Vault list shows a Bar for each vault. It has a caption that says something like
The Bar has hashes on the right side and solid color on the left. I assume this shows The total Drive side, and the total amount of free space availble at that moment, yet it does not show the size of the actual vault. And Green means plenty of room left, red means getting close to full. Dum quesiton but I need varification.
Thank you very much for your patients with a relatively new Aperture User.
Mike

Hello Mike,
All images (and all versions of an image) are stored in one and only one project. All versions of the same image are always part of the same project.
The "Photos" view shows you all versions of all of your images for quick access and filtering and searching, but it does not store the images - it is not a container like the projects, it's more like a smart album.
Then that new "Project" would contain "Versions" of the orginal files in the "Photos" section??
If you drag an image by accessing it from the Photos View, you will not drag it from the Photos View but move it from its original project to a the new project - this does not create new versions in the new project. The Photos View is just a neat feature to select all your images in one place, independent of the project they are stored in, like having a file of index cards to all your images.
If so, then if I delete that new "Project" under "Projects and Albums" it should just delete the "Versions" in that project??? and not the originals under "Library?"
Oh yes, deleting any project will certainly delete your original images. The only originals you see under "library" are projects in the "Projects" view, and that are exactly the same projects as under "Projects and Albums" - just different ways to access the same content.
What I was trying to find out is that if I delete a project, then that grouping created under that project would disappear but the original images would still be in the libary, just no longer assigned to that deleted project.
If you delete a project, from whatever view you use, the images stored in that project are gone. And since each image - and all its versions - belongs to only one project, that image will be removed from the library for good, if its project is deleted!
You really need to get a better understanding of the basic organizational structure of Aperture:
If you not have found it already, here is the User Manual, really worth reading:
Aperture 3 User Manual: http://documentation.apple.com/en/aperture/
and here are well-polished, introductory posts by Kirby Krieger:
Kirby Krieger: The Well-Trod Path:
https://discussions.apple.com/message/16003277#16003277
Kirby Krieger: Re: Organizing in Aperture, concise long version:
https://discussions.apple.com/message/12616449#12616449
Kirby: Krieger: Best way to managing libraries?
Post back, if you need further clarification; I am sure someone else will drop in on this discussion.
Regards
Léonie

Toolbar doesn't have option: "Photos, Shared, Albums, Projects"

The guide says there's supposed to be four options at the top of the toolbar:
But I don't have them:
I'm using Yosemite 10.10.3, BUT I originally installed it as part of the public beta that came with Photos. However, I have since updated to the public non-beta version. Could this be the problem?

The guide says there's supposed to be four options at the top of the toolbar:
If you have the sidebar open you will see the Shared - Albums - Projects in the sidebar.
There are hidden Show/Hide controls to the right of the section titles, so you can show or hide them, if you hover the pointer to the right of the titles.

The last Version in a Project is a Master?

I am reading the Aperture documentation and the Glossary states:
Version: The file containing all the metadata and adjustment information applied to an images, a vidao clip, or an audio clip. In Aperture, only versions are changed. Aperture never changes masters. See also master.
Master: The source media file that was copied from either your computer's file systeem or your camera's memory card. In Aperture, the master is never modified. Whenver a change is made to an image, a video clip, or an audio clip, that change is applied to the version. See also memory card, project, version.
Project: In Aperture the top-level container that holds all the masters, versions, and metadata associated with your shoot. In the cae of referenced images, the masters are stored in their current location rather than in the project file. See also album, folder, library, master, referenced images, version.
I am trying to understand
1. Is this saying that I have /both/ Versions and Masters in my Project in a managed images database (i.e. all images are in the Aperture database)? If so, is there a number of ways to create a version from a master so I can see what this does /and/ is there a way to tell which is a Version and which is the Master if they look exactly the same?
2. If I have /both/ two Versions of a Master and the Master in a Project (three total files) - and assuming they look exactly the same can I just willy-nilly delete two of these same looking images and expect Aperture to just delete two and retain "the" Master? I mean, functionally speaking it doesn't matter which of these three I delete because Aperture will perform a sort of sleight of hand and keep one is that it?
Sorry for all the posts on this but I am trying to read up on this and get work done at the same time and I just don't get this yet.
Thanks,
Jon

OK. Thank you.
Can I please just follow up with you on this? I am experimenting and seeing behaviour I am not sure I really understand.
If I then take these three Versions (all of the same Master) - and I copy them to an Album. I am seeing the following behaviour (from my recollection):
I can DELETE the third Version in the Album (which Deletes the Version in the Project), then I can delete the second Version in the Album (which deletes the second version in the Project), then I can delete the third version in the Album (which deletes my last remaining Version in the Project) - all without any warning or any alert. Is that right? I mean at this point I have no more Master.
Also, I am uber paranoid about deleting things at this point because I trashed my database so badly but I have ALBUMS that have IMAGES in them. SOME of these "Versions" are being used by other ALBUMS because I have STARRED AND COLORED all the Versions in my Albums. Now I know for a fact what I have in my albums and when I look in a PROJECT I know not to delete this or I will screw up my Album.
However, how do I delete an Album without worrying that I am going to delete a "master version" (i.e. trash my last Version in my Project for my master) or that I am going to trash a Version that is being used by another ALBUM?!
Do I just run a DELETE of the ALBUM and this is like REMOVING the Version from the Album in a way that won't trash my Master or my Albums?!
Does that question make sense??

Autonumber formats change after topics are linked across projects

We are going from Robohelp HTML x5.0.2 to Robohelp HTML 8.0.2.208, so there is obviously a huge learning curve that we are working through. We generate to WebHelp and merge 15 projects into a published master. Our users view the output on our intranet using Internet Explorer 7.
We loved the autonumber format feature in version 8 (particularly the additional bullet styles available and no longer needing to manually renumber steps when something was inserted or deleted), but have run into a problem.
The autonumber items work fine in the projects and when generated and published into the merged master, but when we need to add a link from a topic in one project to a topic in another project it changes the bullets and numbering.
Example:
We have a topic in Project A that references a topic in Project B (both projects are part of the merged master).
We insert a link in the Project A topic to the topic in Project B (using Insert Hyperlink - Link To - File). Everything in both A and B look fine at this point.
We preview the topic Project A by clicking on "View Selected Item" (eyeglasses) and then click on the link we inserted to validate it works. This causes the topic in project B to now have stutter-text for bullets and numbers (i.e., what used to say "1. Step" now says "1. 1. Step"). As more links are added to that topic, it adds more bullets and numbers to the linked topic:
1. 1. 1. Procedure
● ● ● Bullet
o o o Bullet2
§ § § Bullet3
□ □ □ Bullet4
This does not happen when adding links to topics that are in the same project, only when linking to topics that are in another project.
All of our topics are created directly in RoboHelp; we do not import files from Word, FrameMaker, etc. Each of our projects has the same style sheet (we created 1 CSS file and copied it into each project so that they were all identical).
All of our version 8 projects were created from scratch in version 8, and we have been importing our version 5 topics one by one (and deleting the version 5 styles assigned to them), then applying the applicable version 8 style to each line. We have attempted creating brand new topics in version 8 to make sure no old legacy version 5 code imported from an old project was causing the issue, and it still happens. We have tried manually cleaning up the HTML code for the topic and it happens again once a cross-project link is added back to that topic. We also tried the "Convert RoboHelp edited topics to HTML" to try to get around the XHTML restrictions and it still happened to everything that was an autonumber format, so it appears the issue is something with that one of these. We created styles for each autonumber format we wanted to use (using the options available for Paragraph styles in the Robohelp Style editor), this is a sample of one of them:
p.Bullet {
 list-style: rh-list;
 x-list-class: rl-p-Bullet;
 x-list-level: 1;
rh-list.rl-p-Bullet {
 x-level-count: 1;
 x-lvl-1-format: "<x>";
 x-lvl-1-type: disc;
While it would be really great to have the additional features of the autonumber format, it may not be a viable option for us since it is only available on the paragraph level and Robohelp 8 does not appear to play well with bullets and numbers in anything other than the list level. I'm thinking I may need to abandon our current style sheet that uses autonumbering and start over with a new style sheet using only the limited bullets and numbering available on the list level (or possibly go old-school and just use the bullet and number toolbar buttons to add formatting to normal text). We are about 8,000 topics into our conversion of 40,000. Any suggestions are greatly appreciated. Thanks!

I'd love to send you the test projects I set up, but unfortunately my company has blocked that ability. I created brand new blank projects in Robohelp 8 using the default style sheet with an autonumber bullet and numbered step added and nothing else. I thought this bare-minimum approach would be the best way to make sure it wasn't something we had set up incorrectly that on our end. I used the default First Topics in each project and added numbered and bullet texts using the style sheet to Project 1 and then added a link to that topic in Project 2. I didn't even generate the projects and I still had the issue when I previewed the Project 2 topic and clicked the link.
I've attached a copy of the info on the topic in Project 1 and the code behind the scenes for it below:
First Topic
1. 1. 1. Procedure
o o o Bullet
o o o Bullet
2. 2. 2. Procedure
Code before link in Project 2:
<?rh-list_start level="1" an="1" class="rl-p-Procedure" ?>Procedure<?rh-list_end ?>
<?rh-list_start level="1" an="1" class="rl-p-Bullet" ?>Bullet<?rh-list_end ?>
<?rh-list_start level="1" an="1" class="rl-p-Bullet" ?>Bullet<?rh-list_end ?>
<?rh-list_start level="1" an="1" class="rl-p-Procedure" ?>Procedure<?rh-list_end ?>
</body>
</html>
Code after link in Project 2 was added and clicked:
<?rh-list_start level="1" an="1" class="rl-p-Procedure" ?>1.     Procedure<?rh-list_end ?>
<?rh-list_start level="1" an="1" class="rl-p-Bullet" ?>o       Bullet<?rh-list_end ?>
<?rh-list_start level="1" an="1" class="rl-p-Bullet" ?>o       Bullet<?rh-list_end ?>
<?rh-list_start level="1" an="1" class="rl-p-Procedure" ?>2.     Procedure
Code after link in Project 2 clicked a second time:
<?rh-list_start level="1" an="1" class="rl-p-Procedure" ?>1.     1.     Procedure<?rh-list_end ?>
<?rh-list_start level="1" an="1" class="rl-p-Bullet" ?>o       o       Bullet<?rh-list_end ?>
<?rh-list_start level="1" an="1" class="rl-p-Bullet" ?>o       o       Bullet<?rh-list_end ?>
<?rh-list_start level="1" an="1" class="rl-p-Procedure" ?>2.     2.     Procedure
Logically there is no reason that clicking on a link that is outside of the project should be able to recode the topic being displayed, but it is.

Edited photos will not save in stacked version after editing

edited photos will not save in stacked version after editing

Thank you problem seems to be solved.
edited photos will not save in stacked version after editing
created by Barbara B. in Photoshop Elements - View the full discussion
Is this PSE 12? Go to editor>Help>updates and apply the 12.1 update, if so.
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at https://forums.adobe.com/message/6417103#6417103
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page:
To unsubscribe from this thread, please visit the message page at . In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Photoshop Elements by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

PSE8 Organizer: Can't stack photos in album view?

Why can't I manually create stacks when I am only looking at photos from a specific album?
For example, if I am showing all photos in the catalog, I am free to multi-select photos and do a right-click >Stack. The same is true if I have filtered the view down by tags, or by import batch. However, if I have selected an album from the Albums list, stacking is no longer an option. Photos that have already been stacked and exist in the album show as stacked, and I can even unstack them (if I right-click the stack, Stack > Unstack Photos is an option, as is Flatten Stack), but if I am not able to create stacks or add photos to stacks. Why is this?

Hi nick,
Checked on PSE10. It does allow stacking when in Album view. However it doesn't allow so in 8 and 9.
You might want to try 30day free trial of PSE10 as it is full of some great features
Here goes the link :http://www.adobe.com/cfusion/tdrc/index.cfm?product=photoshop_elements&loc=en_us
Thanks
andaleeb

Simulation version to Operative project

Hi experts,
I am unable to create an operative project structure from a simulation version using project builder.
My req:
I have sim version: T-90001/ SIM001
I wish to create operative project T-90001
I can use CJV4 for transfer of project. But is it possible in CJ20N?
Warm regards
ramSiva

Hi Ravi
Thanks for your response
Please look at the link http://help.sap.com/saphelp_erp60/helpdata/en/0b/ba853488601e33e10000009b38f83b/frameset.htm
There is an illustration which depicts that,
- Project P1234/version 0001 --> Project 1234 --> Project P1234/Version 0002 --> Project P1234
As per this illustration, the project number remains same.
As you said, the transaction CJ20N is not allowing me to transfer the simulation version to operative project.
But, i am experiencing a dump error while trying to transfer simulation to operative in CVJ4.
At the conclusion, i mean to say that irrespective of transaction code, this may be allowed.
Please comment.
warm regards
ramSiva

Stacks, versions, links, albums, projects, grief.

Similar Messages

Maybe you are looking for