Exhibeo export packages showing as folders

Exhibeo
1

Has anyone had any issues with either the Exhibeo update or Freeway updates somehow breaking Exhibeo export files? I have about a dozen Exhibeo galleries saved as .exhibeo projects and exported to Freeway as .xbExport packages. Since the updates I have made two new galleries and uploaded the site to the server once with the addition of the two new galleries.

I went to work on my FWP file today and noticed some inconsistencies with a few things and so went to edit my resources and resample as necessary… turns out all of my original Exhibeo exports are no longer in packages in the Finder but rather regular folders so FWP cannot find nor let me resample/update/locate/re-import via Exhibeo action. File extensions have not changed.

It seems as though the two galleries I made after the updates are showing just fine as packages and working as expected.

It seems crazy to me that an application update could effectively break existing files it has created… but I can’t seem to find another cause or explanation for it… and certainly no way to rectify it except to re-export all the galleries and re-edit the css for each to reflect my original changes. And then what happens when there’s another (albeit much appreciated) update?

(The same has happened to a single gallery on a separate site that I have opened but not worked on since the update.)

Thanks!

D

Exhibeo mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

2

Hi,

When Exhibeo exports “to Freeway”, it sets what’s called the bundle
attribute on the folder, telling Finder and anything else that it should be
displayed to the user as if it was a file. As you’ve observed, the Action
wants a bundle and so the folder can’t be selected if the open panel isn’t
presenting it as a bundle for whatever reason.

My suspicion is that somehow this bundle attribute has been lost. Open the
Terminal application and type the following, followed by a space, then drag
one of your non-working .xbExport folders on to the Terminal window:
GetFileInfo -ab

So it should look something like this:
GetFileInfo -ab /Users/simon/Desktop/test.xbExport

Hit enter and you should get either a 1 or 0 and if it’s a 0, this’ll be
why it’s showing up as a folder. Possible reasons could include running
“Fix Permissions”, (I doubt it myself but it’s a bit of a black box)
zipping and unzipping the exports or moving between machines. They should
be fine just running OSX with the built-in tools but there is potential
with third party tools or moving via a non-OSX machine.

I’ll be surprised if you get a 1 from the previous command for one of the
exports showing up as a folder but I’ll be interested to know if you do.
You can set the attribute again using this command, again with a space on
the end and dragging the file on to Terminal:
SetFile -a B

-Sim

On 9 March 2015 at 06:41, dmrooney email@hidden wrote:

Has anyone had any issues with either the Exhibeo update or Freeway
updates somehow breaking Exhibeo export files? I have about a dozen
Exhibeo galleries saved as .exhibeo projects and exported to Freeway as
.xbExport packages. Since the updates I have made two new galleries and
uploaded the site to the server once with the addition of the two new
galleries.

I went to work on my FWP file today and noticed some inconsistencies with
a few things and so went to edit my resources and resample as necessary…
turns out all of my original Exhibeo exports are no longer in packages in
the Finder but rather regular folders so FWP cannot find nor let me
resample/update/locate/re-import via Exhibeo action. File extensions have
not changed.

It seems as though the two galleries I made after the updates are showing
just fine as packages and working as expected.

It seems crazy to me that an application update could effectively break
existing files it has created… but I can’t seem to find another cause or
explanation for it… and certainly no way to rectify it except to
re-export all the galleries and re-edit the css for each to reflect my
original changes. And then what happens when there’s another (albeit much
appreciated) update?

(The same has happened to a single gallery on a separate site that I have
opened but not worked on since the update.)

Thanks!

D

Exhibeo mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

3

Hi, Simon —

Absolutely brilliant, thank you! I tested as you recommended and did get a 0 and was able to successfully reset the attributes for the files as well. I did have to move some things around due to some storage issues I thought this might have broken the bundles, however as it only affected certain exports, the only other difference between the bundles were the Exhibeo/FWP updates. Either way, glad to have a sensible way to fix the issue, and to have another great trick up my sleeve!

Thanks again!

D

On Mar 9, 2015, at 5:45 AM, Simon Manning email@hidden wrote:

Hi,

When Exhibeo exports “to Freeway”, it sets what’s called the bundle
attribute on the folder, telling Finder and anything else that it should be
displayed to the user as if it was a file. As you’ve observed, the Action
wants a bundle and so the folder can’t be selected if the open panel isn’t
presenting it as a bundle for whatever reason.

My suspicion is that somehow this bundle attribute has been lost. Open the
Terminal application and type the following, followed by a space, then drag
one of your non-working .xbExport folders on to the Terminal window:
GetFileInfo -ab

So it should look something like this:
GetFileInfo -ab /Users/simon/Desktop/test.xbExport

Hit enter and you should get either a 1 or 0 and if it’s a 0, this’ll be
why it’s showing up as a folder. Possible reasons could include running
“Fix Permissions”, (I doubt it myself but it’s a bit of a black box)
zipping and unzipping the exports or moving between machines. They should
be fine just running OSX with the built-in tools but there is potential
with third party tools or moving via a non-OSX machine.

I’ll be surprised if you get a 1 from the previous command for one of the
exports showing up as a folder but I’ll be interested to know if you do.
You can set the attribute again using this command, again with a space on
the end and dragging the file on to Terminal:
SetFile -a B

-Sim

On 9 March 2015 at 06:41, dmrooney email@hidden wrote:

Has anyone had any issues with either the Exhibeo update or Freeway
updates somehow breaking Exhibeo export files? I have about a dozen
Exhibeo galleries saved as .exhibeo projects and exported to Freeway as
.xbExport packages. Since the updates I have made two new galleries and
uploaded the site to the server once with the addition of the two new
galleries.

I went to work on my FWP file today and noticed some inconsistencies with
a few things and so went to edit my resources and resample as necessary…
turns out all of my original Exhibeo exports are no longer in packages in
the Finder but rather regular folders so FWP cannot find nor let me
resample/update/locate/re-import via Exhibeo action. File extensions have
not changed.

It seems as though the two galleries I made after the updates are showing
just fine as packages and working as expected.

It seems crazy to me that an application update could effectively break
existing files it has created… but I can’t seem to find another cause or
explanation for it… and certainly no way to rectify it except to
re-export all the galleries and re-edit the css for each to reflect my
original changes. And then what happens when there’s another (albeit much
appreciated) update?

(The same has happened to a single gallery on a separate site that I have
opened but not worked on since the update.)

Thanks!

D

Exhibeo mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Exhibeo mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options