Possible Keyword Bug

Okay,
I think I have found a possible bug with keywords, or maybe just an incositancy. It's kind of a messy situation so I'm hoping someone can help me out or maybe point me in the right direction to send this feedback to Apple.
I had a bunch of jpeg files from my older cameras that had already been tagged with keywords (in the IPTC keyword field I believe). Once I imported all of these into Aperture I stripped the keywords from all the images. That worked fine.
Before I get into the actual issue let me give a little bit of information on my Aperture library layout: I have folders created by year, then 1 project per month. So I have something like this:
2002
01 Janurary
02 Feburary
2003
01 Janurary
What's weird is if I create a new smart album at the folder level, the keywords listed in the search box are appropriate (only those actually added to images). However if I click on Library and create a new smart album (so that it searches the whole library) it lists all of my current keywords, plus all of those that I had removed (from the original files).
Anyone else run across this? Anyone know how to fix it? It's just a minor inconvience, but it does make it a bit of a pain to have a whole ton of keywords to select from in the search box (most of them no longer having any images associated with them).
Also I have searched for images that match the old keywords and it doesn't find any.
Thanks,
Mark

She suggests..
"Go to Window > Show Keywords HUD, and see if they are there. If so, you should be able to delete them from there."
Hopefully, they will then disappear from the Library list.
if not, it does seem like a bug.
Message was edited by: notorious

Similar Messages

  • Library Keyword Bug - Another example

    Lightroom v 3.3
    iMac  OSX 10.6.7
    Here is another example, a pretty egregious example of the keyword bug.
    Keyword:  Linda shows 811 photos
    The Library Filter Shows 801 photos
    LR opens 599 in the grid view.
    What gives?

    I hit Photo > Stacking > Expand All Stacks before taking the screen shot.  I brought in 15 more photos.  But there still is a big discrepancy between the keyword count, and the filter count on top.
    Any experient or suggestions.  I DO NOT want to rebuild everything, it will take me weeks.

  • Keyword Bugs and Some Keywording Improvement / Feature Suggestions

    Tagging Bugs and Some Improvement / Feature Suggestions
    Please excuse where I should use the word Tag or Keyword or vice versa!
    1.       BUG?    If a tag synonym is added or changed then all affected photos should be marked for re-publish.  I do not think this currently happens.   Should this possibly be considered a bug?
    2.       BUG?    When viewing a smart collection in a Flickr publish service and a new tag is added to a photo it is correctly moved to the “requires re-publish” section.   However … the thumb selection in the grid moves to the next photo, the loop view remains on the photo just tagged and the key wording still reflects the just tagged photo.    The selection shown in the grid appears to be wrong.      When working quickly this can result in tagging errors as the user looking on the grid believes he is working on the next highlighted photo in the grid.      This is surely a bug?
    3.       BUG?      A minor point and I realise this is probably not the correct way to do things … but a double word synonym entered with quotes for example “Ice Climbing” will create two tags “Ice” and “Climbing” at the flicker end of things.    Removal of this synonym and forcing a re-publish does not delete these two tags at the flicker end of things.    I may have miss-understood, but perhaps it is best for LR not to allow quoted tags? 
    4.       SUGGESTION      An easier and more powerful way to review tagging of current photos should be provided whereby it is possible to clearly see the current tagging of a photo and have immediate access to the keyword list at the same time to make corrections.    Having both the Keywording and Keyword List panels open in Library mode results in a lot of up and down scrolling for me and is a slightly inelegant UI in my opinion.   I would suggest it should at very least be possible to have the tags viewable in Loop info as an option - so long as no truncation is made and all tags visible.    Ideally a better way should be sought.
    5.       SUGGESTION      It would be very useful when reviewing tagging to select to show all photos in the currently selected folder or set which do not contain the selected tag.    Note, I don’t think this can be easily achieved by using a keyword filter and selecting all keywords and unselecting the tag of interest as the pictures may have many tags.    The same might be performed by textual based searches but this is inelegant and its slowness precludes a browsing approach.     For example – for me it would be useful to look at all my mountain shots in a trip which have not been tagged with “Glacier” and it will be immediately visually apparent where I need to make tagging corrections.    I would suggest a “Not” checkbox is made available on the top of each column in the library filter – this may also provide a great deal of power for other situations.
    6.       SUGGESTION      It would be useful to allow a means of showing all pictures with a certain tag but which have not been tagged yet with any children of said tag.   For example all pictures tagged with Glacier which I have not yet named the glacier by introducing a relevant child tag or selecting an existing child tag.    A similar situation occurs for wildlife and potentially many other scenarios … I would like to use a tag “Butterfly” which I can quickly use on my first pass… and then do the identification and child tagging on a second pass using appropriate filtering.   This allows for a step wise or “top down” approach to tag classifying things in a workflow.    I appreciate this can be achieved (as I do now) by using a child tag called “Unnamed butterfly” or “Unnamed Glacier” but it seems more powerful, elegant and generically applicable to be able to filter on a “not tagged with a child” basis.
    I apologise if I have missed the point on some existing functionality on any of these points and welcome any suggestions.

    This is a great post.
    I couldn't have written it myself better.
    I'm also in dying need of Korean input as I can't communicate with my Korean friends.
    But I second every point.
    I hope the tech teams are reading this.

  • Smart Album Keyword Bug

    I have a library of 17,440 “Referenced” photos, grouped across multiple projects, none of which contain more than about 400 photos. Prior to importing these images into Aperture, I had already keyworded all of them; the keywords are embedded within the image files.
    707 of these images have the keyword “Cruise_Ship” (photos of or on a cruise ship). I then created a smart album with a SINGLE filter, “Keyword = Cruise_Ship”. I have no other filters selected, I have no other keywords selected in the keyword filter, and at the top of the keyword filter, I have selected “Include ALL of the following”.
    However, instead of the 707 expected images, this smart album actually displays 5336 images. I have verified, via the metadata browser that in fact most of these images DO NOT contain the keyword “Cruise_Ship”.
    So, I tried the following (in order). After each step, I once again checked the contents of the smart album, and in each case it displayed 5336 images instead of the correct 770:
    Repair Database
    Repair Permissions
    Rebuild Database
    Reboot Computer
    Rebuild Database
    As one last attempt, in the Keyword HUD, I renamed the keyword “Cruise_Ship” to “CruiseShip” (no underscore). The HUD correctly indicated that that keyword was used in 707 versions. I then in fact changed the keyword in those versions. I then created a NEW smart album, with the only filter being “Keyword = CruiseShip” (again no underscore) and once again the smart album incorrectly displayed 5336 images.
    I am using Aperture 3.0.3.
    I’m out of ideas...

    I can't say I have the same bug. However, I do have one that might be worth checking on.
    On my Aperture 3 here the keyword panel padlock works back to front, i.e. if it's displaying an open padlock icon, the keyword panel is actually locked, rather than unlocked as it should be, and vice versa.
    This stumped me for a while, as I also kept finding unauthorised changes happening to my keywords. Now I know to operate the padlock opposite to what I expect, it does stop any unauthorised changes.
    (yes, I submitted a bug report).
    Cheers.

  • Library Keyword Bug?

    I am not sure if this is a bug, and if it is not, then I suppose this will be a feature request.
    Background: I am using Lightroom 1.3.1 on a MacBook Pro 2.4 GHz on OS X 10.5.1 with 4GB of RAM.
    Expectation: When in the Library Module, I'd like to be able to select multiple files from the thumbnail bar at the bottom, type in applicable keywords and then save them to all of the ones selected regardless of whether my main screen is in fit mode or thumbnail mode.
    Actual Experience: When the main screen is in fit mod and I save my keywords, they only save to the actual image being displayed in fit mode despite the fact that I have multiple images selected below in the thumbnail bar.
    Thanks,
    Stephen

    Searching in this forum defaults, unfortunately, to the thread you've just been perusing. Just check the other box.
    BTW, if we were to vote on it, I'd go with the way it's set up currently. But then, for whatever reason, I hardly ever use the strip. Much prefer grid for multiple ops, and for me, I need to check just how many are selected, anyhow!

  • Thinkpad S540 possible BIOS bug concerning WOL

    I have had a Thinkpad S540 for a few months, and have it installed as dual boot Windows 8.1 and arch linux.  After completely shutting the machine down from linux I found that the battery would be down to around 70% charge after three days unused, and decided to investigate this problem since it was not reasonable for a new battery to lose charge at anything like this rate.
    By chance I came across a piece of information concerning the issue of disabling WOL (Wake on LAN) on the network interface, since I had seen one report that by default WOL is enabled and this requires power to be going to the network interface even when shut down in order to be able to respond to magic packets to start the machine up when it is shut down.
    First I checked the BIOS WOL setting and found it was set to "AC only" by default. So I changed it to disabled. This machine has the latest available BIOS version 1.54.
    However on investigating this after rebooting in linux I found that 
    # cat /sys/class/net/enp3s0/device/power/wakeup
    enabled
    # ethtool enp3s0 | grep Wake-on
    Supports Wake-on: pumbg
    Wake-on: g
    So WOL was still enabled despite it being set to disabled in the BIOS!
    I learned that I can make sure that in arch linux the WOL setting can be changed to set to disabled after bootup by using a udev rule:
    # cat 70-disable_wol.rules
    ACTION=="add", SUBSYSTEM=="net", KERNEL=="enp3s0", RUN+="/usr/bin/ethtool -s enp3s0 wol d"
    Then rebooting the machine I checked the WOL setting and it really is disabled now:
    # ethtool enp3s0 | grep Wake-on
    Supports Wake-on: pumbg
    Wake-on: d
    # cat /sys/class/net/enp3s0/device/power/wakeup
    disabled
    So I then ensured that the battery was 100% charged and shut down the machine and left it two and a half days - rebooting this morning the battery was still at 100% charge and no longer discharges unnecessarily when the machine is switched off,  so this is a clear indication of a bug in the BIOS for the WOL setting - it is still enabled despite the BIOS saying it is disabled!
    How do I report this to Lenovo so that they can fix the BIOS and release a new one that is working?
    I am aware of other users with different Thinkpads who seem to have the same problem, so this may be more widespread an issue than just on the S540.  
    It is also not just an issue with the battery running down when fully shut down but will likely also be a problem for a machine in suspend mode since the network interface may be consuming a watt or so of power when in suspend, which will again run the battery down at an unacceptable rate.
    I cannot imagine any use case where it would be necessary to have WOL enabled on a laptop that is mostly going to be used mobile - so having the default setting to AC only enabled, and having a BIOS bug enabling it when it is explicitely disabled is a serious problem.

    Anyone running windows in the same laptop can check the same issue of battery drain due to WOl being enabled by default - in the Device Manager under the network card, opening the settings menu for the ethernet wired card the default for Wake-on-LAN on my computer was set to enabled. This can be changed to disabled, and you may need to also disable the setting for Wake on Magic Packet. Also in the Power Management tab it is possible to uncheck the settings for "Allow this device to wake the computer" and "Only allow a magic packet to wake the computer"
    In my laptop these were all set to enabled by default.

  • Filter by keyword bug?

    Has anyone else noticed this bug in iMovie '09...
    After adding some keywords try to use the 'Filter by Keyword' feature, you'll notice that it's impossible to turn the topmost green light on. In other words it's impossible to 'only show clips that are tagged with whatever happens to be the first keyword in the list'.
    You can only 'omit' the topmost keyword from view (red light).
    Dave

    I've noticed this as well - surely this can be sorted in a software update? What are your plans Apple?

  • Possible code bug causing crash on Wine/Linux

    As I am running Linux, I don't expect support as such but thought I would offer a possible contribution to the beta program as follows:
    When starting Safari under Wine (an implementation of the Win32 API) on Linux, I get the following debug message:
    DIB_GetBitmapInfo (44): unknown/wrong size for header
    What I understand this to mean is that the Windows function GetBitmapInfo is being passed a dodgy parameter.
    This is followed by a crash for me, but I guess on Windows, is quietly ignored.
    I have seen a report on CodeProject regarding an identical crash caused by a coder setting the biSize member of the bmiHeader (BITMAPHEADERINFO) element of a BITMAPINFO structure to the incorrect size. In the example given, it had been set to sizeof(BITMAPINFO) rather than sizeof(BITMAPINFOHEADER)
    e.g.
    bmpInfo.bmiHeader.biSize = sizeof (BITMAPINFO);
    instead of
    bmpInfo.bmiHeader.biSize = sizeof (BITMAPINFOHEADER);
    For any devs. interested as to whether there may be a bug, the call stack generated by Wine, showing the offsets from the base address of coregraphics.dll (loaded at 0x6b000000) is as follows, with the crash actaully occurring at '=> 1'
    Backtrace:
    =>1 0x6b262e97 in coregraphics (+0x262e97) (0x0033ed38)
    2 0x6b0f9da4 in coregraphics (+0xf9da4) (0x0033f31c)
    3 0x6b1e0fff in coregraphics (+0x1e0fff) (0x0033f4bc)
    4 0x6b1d19ee in coregraphics (+0x1d19ee) (0x0033f578)
    As I say, I'm not expecting any feedback on this - I'm just being neighbourly I also fully accept that I may be completely wrong in my assessment of the issue.
    Dell Inspiron   Other OS  

    There was an even earlier build than the two mentioned.
    Talk about "early revisions" I guess so, and it doesn't look like there will be a unified version tomorrow.
    I recall AYM had a note about video performance and in that instance, the build on the DVD was never than what was on the hard drive and within a week or so disk drives carried the "new, improved" video on disk as well.
    There may be other changes that go hand-in-hand other than build, too. Did they look at the Boot ROM and SMC Version of the systems?
    Boot ROM Version: MP11.005C.B00
    SMC Version: 1.7f6

  • Possible Tab Bug?

    The current bug: Adding an additional tab below another will cause the tab to looked messed up. The work around suggested was to create a page (with new tabs), publish it as a portlet underneath a main tab. Then you will visually see tabs underneath tabs.
    The new problem you get with this work around is your content underneath the sub-tab will not show up the first load. You have to click on another tab, then back to the previous tab to show the content.
    Another weird thing I ran across having to do with regions and published folders. I found that you cannot set a corrent percentage within regions when folders are added to regions.
    For instance; Under a tab, divid a region into two regions. The first region make 5% and the second 95%; now when you add your (folder) portlets underneath both regions you will see when viewing it, that it will show up 50% and 50%. If you take out the folder portlet on region 1, and add a application portlet; everything shows up fine.
    I have come across varies things like this, but I will start posting the errors and possible work arounds.

    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>The new problem you get with this work around is your content underneath the sub-tab will not show up the first load. You have to click on another tab, then back to the previous tab to show the content.<HR></BLOCKQUOTE>
    I noticed this also. (in 3.0.6.7.2 on NT).
    What's funny about this is that this is exactly the same as a bug with sub-tabs in the EA release. Maybe the data structure of a sub-tab and a page in a tab is very similar...
    null

  • Foreach syntax + generics, Possible compiler bug?

    I'm encountering an odd problem trying to use generics and the foreach (colon) syntax. The code in question:
    for (Iterator<String> it = col.getParameterNames().iterator(); it.hasNext();) {}
    for (String paramName : col.getParameterNames()) {}col is an instance of an inner class of the class whose method this code snippet is from, getParameterNames has the signature:
    public Set<String> getParameterNames();
    The first line, using the Iterator<String> explicitly, compiles fine. The second line, when present, raises the compiler error:
    found : java.lang.Object
    required: java.lang.String
    for (String paramName : col.getParameterNames()) {
    I cannot seem to reliably reproduce this situation in other (simpler) classes I write, but this one in particular seems to trigger it. Is it possible this is a compiler bug, or might there be something I'm doing incorrectly that I'm missing? Are my expectations about how the second line should work incorrect? It seems to in other circumstances...
    javac is 1.6.0_01. Any ideas?

    Here is a quick update, I'm more inclined to think of this as bad behavior now.
    This code compiles:
    public class Test {
    Vector<InnerTest> inners = new Vector<InnerTest>();
        public class InnerTest {        
           public Set<String> someSet() { return (new HashMap<String,String>()).keySet(); }
        public Test() {
            for (InnerTest it : inners) {
                for (String s : it.someSet()) {        
    }however, the following does not:
    public class Test {
    Vector<InnerTest> inners = new Vector<InnerTest>();
        public class InnerTest<P> {        
           public Set<String> someSet() { return (new HashMap<String,String>()).keySet(); }
        public Test() {
            for (InnerTest it : inners) {
                for (String s : it.someSet()) {        
    }Again, the problem might be with my expectations (I haven't gone through the specifications yet with this in mind), but I can't fathom how or why the unused parameter would make a difference in that method's tpye matching.

  • How It Was Fixed (Possible Software Bug Not Hardware): Getting the iMac Screen/Menus Garbled and/or Yellow Circle Before Getting Into Finder Issues?

    Hi. Possible fix done to my late- 2009 iMac's screen/graphics issue that may work God willing, hopefully for most [In my case it sometimes had that yellow circle that appears before it goes to the Finder but mostly it was a messed up desktop and menus (unreadable mostly) after months, prayers and weeks of fixing it; recommended to be read entirely first coz' it's a bit complicated (like a lot of subplots). If uncomfortable to try coz' it involved a GPU stress test, contact your authorized Apple service center for their advice]. I had an iMac (late 2009) screen garbling a few hours ago (was weeks ago when it resurfaced until it got worse that it's at every boot on Mavericks):
    †        I booted to Snow Leopard USB external (my back-up OS) drive then run the first    person shooter at redeclipse.net. I set everything to max, including the display, resolution and graphics setting with fullscreen and v-sync on. I then refreshed it which brought it back to normal (I then tested it's stability with GPUTest 0.7 with Furmark for 15 minutes). * if the display options have been set to max before, bring it back to the default then refresh and then max it again Possibly any games that's has the graphic settings (or more advanced) of Red Eclipse could work (other free ones are Xonotic and Open Arena which are based on Quake 1 or 3s engine I believe).
    Optional but not recommended (have warrantied if that's still available or have it repaired at authorized service centers):
    If that doesn't work, review articles and videos on how to open an Intel iMac and get an iPhone/iPad/another way to get to the 'net ready for research (I opened mine very carefully on the right side with a cutter with blade extended far prying it carefully then I inserted a flat end, sturdy plastic used for mixing epoxy then removed the cutter carefully to let the plastic mixing tool do the prying) to see if the cable connected to the logicboard which is on top of, is connected (mine was detached but I'm not sure if the adjusting and tilting of the screen overtime for 2 & 1/2 years, detached it) then do † above again.
    It could to be a software problem, a possible Apple ATI driver bug that takes overtime to surface (2 1/2 years it resurfaced because this started in my case after upgrading to Lion when Apple coded things mostly from the ground up. Snow Leopard didn't have this problem). 
    Thank you for your time. Have a great upcoming sunday mass/great upcoming weekend. I hope this helps.
    God bless, Rev. 21:4, Matt. 16:18

    Does an external display also act in a similar manner as the internal one?
    Some earlier Intel-based iMacs had graphic processor card issues; not sure what
    the symptoms of the majority of them were, but some had odd patterns, others
    went black, and some would range from OK to totally unusable. Among others.
    So there is a chance the graphic processor may be going out; or just the circuitry
    that controls the backlight. An inverter may be weak or other circuit to the display
    could be wearing out.
    http://www.apple.com/retail/geniusbar/
    If you have access to an Apple Store with Genius bar, they can perform some kinds
    of diagnostic tests there even though the computer is out-of-warranty; that may be
    of help to narrow down the cause of the symptoms you've noticed. They may not be
    able to repair it, however, at an Apple Store; as it is rather old by today's standard.
    An Apple Authorized Service Provider could do repairs and testing on older models
    the Apple Store's Genius and other may not be set up to handle due to vintage.
    Find an Apple Authorized Service Provider
    Visit an Apple Retail Store
    There is a country locator page to help find either of the above in regions outside
    of the US & Canada, not sure how the above links would work; and it appears my
    bookmarks to the country locator page may not be accessible now to post here.
    You may be able to get an idea about what kinds of parts support the display
    function by name by looking into an iFixit.com repair guide for your iMac series.
    Hopefully the parts supporting the display are the reason it is dimming down, as
    a graphic processor failure likely would exhibit other behaviors than just dimming.
    PS: I see you've added content to your thread after I'd started working on this
    & the answer likely is a hardware repair; professional testing is worth the time
    and you seem to have at least one other thread on the same topic....
    Good luck & happy computing!
    edited 2x

  • Possible "unlock" bug

    Greetings.
    I decided to post this here, as I dont have developer access for bugreporting site.
    Using "The new iPad 3" with latest iOS 7.1.2
    I found a strange bug by accident. I can repeat it, although it doesn't always work out.
    Here it goes: When I turn my iPad on from black screen to start screen and slide unlock
    bar like this (Finnish language set)
    If I stop there (correct spot changes and not always the same) and then flip iPad, so
    screen turns automatically (up and side both works).
    This will result so, that unlock bar is stuck and I can't open iPad anymore. Not without turning
    power off and then back on. This problem came with 7.0+
    Would be intresting to know, if this is known thing and can others repeat this with other
    iPads?
    Thanks for your time.

    I would suggest getting a copy of wireshark and see if the browser is behaving, I have seen
    lots of issues where the server is closing the connection and Safari still tries to send more data, which
    violates the RFC. You would also notice lots of tcp connections being opened possibly as well if the
    site finishes loading. I have been trying to use Safari exclusively for a while, but somehow I always end up in Firefox. Hopefully they will have most of the gotcha's under wraps soon, but until than their is always
    Firefox.

  • Semicolon Keyword Bug

    I just submitted this as a bug to Apple:
    I have keywords set to have people's names listed last name first. So to keep Aperture from treating the last and the first name as separate keywords I format them as "Smith; Fred" instead of "Smith, Fred". This works most of the time, if "Smith; Fred" is not the first keyword to be added to an image.
    I've discovered though that if "Smith; Fred" is the first keyword and I add a second. say "Friend", (it doesn't seem to matter what the second keyword is), Then "Smith; Fred" gets split up into two keywords. So in the metadata viewer it is listed as "Fred, Friend, Smith", but if I click on the Keyword tab below the Metadata Viewer, it is still listed as "Smith; Fred" and whatever hierarchy structure listed to the left.
    When I try to remove all the keywords by pressing Shift 9, all the keywords in the Keyword tabs are removed including "Smith; Fred", but in the Metadata Viewer "Fred, Smith" remains. I have to either manually remove "Fred" and "Smith", or use the Batch Change function to clear the lingering keywords.
    If I add "Friend" as a keyword before I add "Smith; Fred", then "Smith; Fred" stays intact, and I can continue to add keywords without "Smith" and "Fred" getting separated.
    If I add "Smith; Sally" as the first keyword, then "Smith; Fred" as the second, I get "Sally, Smith, Smith; Fred" as the result in the keyword viewer, instead of what I should get "Smith; Fred, Smith; Sally"
    I can only reproduce this when using commas or semicolons. So adding "Smith, Fred" or "Smith; Fred" gives you these results. I understand that because commas are the delimiter for keywords they should be avoided.
    All of these combinations do not reproduce these results and can be used without "Smith" and "Fred" becoming separated:
    Smith Fred
    Smith: Fred
    Smith. Fred
    Fred Smith
    I can use "Smith Fred" or "Fred Smith" in my keyword HUD and arrange them alphabetically by last name, but I find listing last name first separated by something other than a space (preferably a comma and failing that a semicolon) much easier and better suited for my purposes. I would appreciate a fix at least for the semicolon so that I don't have to be careful about the order that I add keywords in.

    To easily remove a keyword from multiple photos at one time do the following;
    1 - select the photos you want to work on.
    2 - bring up the Keyword pane (type Commande+K)
    3 - find the keyword you want to remove (it will be in blue) and click on it. When it turns grey the keyword will be removed from all of the selected photos.  You can add keywords the same way.
    See if this method will permanently remove the keyword(s) from the photo.
    If that doesn't help make a temporary, backup copy (if you don't already have a backup copy) of the library and try the following:
    1 - delete the iPhoto preference file, com.apple.iPhoto.plist, that resides in your
         User/Home()/Library/ Preferences folder.
    2 - delete iPhoto's cache file, Cache.db, that is located in your
         User/Home()/Library/Caches/com.apple.iPhoto folder. 
    Click to view full size
    3 - launch iPhoto and try again.
    NOTE: If you're moved your library from its default location in your Home/Pictures folder you will have to point iPhoto to its new location when you next open iPhoto by holding down the Option key when launching iPhoto.  You'll also have to reset the iPhoto's various preferences.
    If still not working  launch iPhoto with the Option key held down and create a new, test library.  Import some photos and check to see if the same problem persists.
    OT

  • Possible Liquid Bug: Moving data into e-commerce layout

    Liquid will not seemingly pass any data from outside an e-commerce layout into an e-commerce layouts is intentional or a bug.
    If you create an include place it in a template then try to pass any data ie assign into any ecommerce layout it does not work.
    If you need more help with reproducing this let me know.

    What I have is a gloabal.inc this contains liquid that I would like to be used across a site ie url manipulations date manipulations and many many more. This is inside a head.inc placed at the very top of the template pages.
    What this means is that the global.inc gets rendered first before anything else. You can then run liquid return results and then use it over and over with a simple {{myResult}} tag almost anywhere on a site. It works great, it is simple, fast to implement and has many applications. I can even create a library of .inc liquid files and can place their include's at will in global.inc and then access variables across a site to add and remove functionality. (Of course this is dependant on what you want to do and if it really needs to be global of course.)
    I get that it is dependant on the way BC loads but if that is the reason then the ecommerce must render before the page template. Maybe it does, maybe there is another reason. If it is possible then it would be great to have working.
    Is there other ways to get the result I want yes. But is it as simple, as fast and as easy to implement, add and remove no. If there is a better way I am all ears.

  • Aperture Keyword Bug!!?!?!?

    Wow, I've just spent hours assigning keywords in Aperture and the Smart Album I've created and re-created does not accurately reflect the selected keywords.... OUCH! Is this a known bug? Please, is there a solution???
    I have noticed that one KW: "Debbie" seems to show all of the images that are tagged with another KW ("Wine"). Some KWs seem to be accurate.... for others there is no explanation--it's just wacky.
    AP 3.0.3, MacPro, 30" Monitor.
    Thanks,
    Robert
    <Edited by Host>

    Also make sure to give Aperture some processing time. With thousands of photos and changes, it can take a minute or more for everything to percolate through the database. I've noticed this especially with mass keyword changes. Close and re-open Aperture to force all changes to take effect.
    In case you don't know, "{Option}+click" on a keyword in the keyword list of the Keyword Filter Rule will deselect all other keywords and select only the clicked keyword. This can be useful for troubleshooting Smart Albums which aren't behaving as expected.
    You should also check that you don't have duplicate keywords with the same name at different levels of your keyword hierarchy. ("People/Friends/Debbie" is not the same as "People/Debbie" even though each shows as "Debbie".) Aperture has yet to correct this unhelpful behavior.

Maybe you are looking for