You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 29 Next »

PF Enterprise FAQ

Common questions about setting up and maintaining a PF Enterprise site.


Umbraco & FTP Access

Umbraco: http://pages.photofinale.com/umbraco/
FTP: ftp://pages.photofinale.com

Your credentials for both will be provided by your account manager.


Content Cache

Changes to content made within Umbraco or to files in your FTP directory can take some time to show up on the site due to caching.

Type

Cache Duration

Changes to Umbraco Content

Up to 60 Minutes

Changes to FTP Content

Up to 15 Minutes

After making an HTML change in Umbraco and publishing it, to complete the publish the central cache must be cleared through myLab.

  • Log into myLab using your Lab 50 Dealer Credentials
  • Go to Store Management, then select Cache
  • Click on the Flush button

We found some scenarios (particularly if you flush a lot) where an Umbraco object could be in the cache, but not on the list of files which we think is in the cache.  Therefore when you hit the Flush button, it is not getting removed (since it wasn't on the list).  If you think this is happening with a page you are working on, we now have a text box where you can enter the page name to have it flush a single item from the cache by name.  Since it's being done by name, it will get the item removed from the cache (if it's in there) regardless of whether or not it's on the official list of files. 

Names are entered like this: PageParts\FooterBody  or if you are working on the content for your landing/main page, you will enter: default.aspx

To facilitate development, you can point your browser to our sandbox server, which only caches Umbraco content for 1 minute (after you have flushed the cache via myLab). This makes rapid-fire change-and-test cycles much easier.

You can hit the sandbox version of your site at any time by using the address: https://*yoursitename*.pfsandbox.com.


CSS Styling

We strongly recommend that you provide an appropriate css namespace scope for your styles to ensure they do not conflict with the default Photo Finale styling.

In practice, this simply means placing all of your custom content in a <div> with a unique parent class name, for example:

<div class="dealer-name">

[ CUSTOM CONTENT ]

</div>

Then each style defined in your CSS file should use that parent selector to define the styles. Setting the font-size of the <legend> element, for example will look like:

.dealer-name legend {
      font-size: 16px;
}

Your style sheets will always be included after the default Photo Finale style sheets, so it is therefore possible for you to override any of the default PF styling by omitting the .dealer-name scope, for example:

legend {
      font-size: 16px;
}


We recommend against overriding the default Photo Finale styling, except as noted below. Lucidiom cannot take responsibility nor provide engineering resources to help diagnose or debug problems caused by overrides to the default styles. Ensuring that the default styling is compatible with all supported browsers on OS X and Windows is enough fun for us already!


Most PF Enterprise sites will need to override certain PF layout styles, shown here. The values of the #header.pageLayout height and #content.fullpage top should be the same and should represent the actual height of your header content.

/* Photo Finale Overrides */

#pageWrapper {
      background: none;
      box-shadow: none;
      max-width: 100%;
}

#header.pageLayout {
      background: none;
      height: 78px;
      border: none;
}

#content.fullpage {
      top: 78px;
}

#footer {
      background: none;
}


Reserved Page Names

The following names are reserved by Lucidiom and should not be used as page or folder names within Umbraco. This list may change from time to time.

  • account
  • addphotos
  • ccvinfo
  • changepassword
  • checkout
  • confirmation
  • create
  • default
  • forgotpassword
  • get
  • getstarted
  • gift
  • gifts
  • guest
  • home
  • link
  • members
  • membershipinfo
  • migrateuser
  • mycart
  • mycollections
  • myfeeds
  • myorders
  • myphotos
  • orderhistory
  • optout
  • photo
  • photos
  • photofeed
  • prepaidplans
  • pricelist
  • print
  • prints
  • projects
  • share
  • shop
  • signin
  • signout
  • signup
  • signupcomplete
  • startsharing
  • terms
  • trackmyorder
  • trackorder
  • transferconten
  • unsubscribe
  • upgrade
  • user


JavaScript Libraries

Photo Finale includes a number of JS libraries. Umbraco content that includes these same libraries (or different versions of them) will likely cause conflicts and should be avoided.

  • ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js
  • ajax.googleapis.com/ajax/libs/jqueryui/1.8.19/jquery-ui.min.js
  • json2.js
  • jquery.fancybox-1.3.4.js
  • jquery.blockui.js
  • jquery.linq.js

The versions included are updated regularly. We'll endeavor to keep this page up-to-date, but you can always verify by simply doing a View Source on one of your pages in PF Enterprise.


Customer Sign-In

There are several methods available to hook up a "Sign In" link to

  • Method 1 - CSS:
    Give your <href> an html id of "signInLink" and class of "no-user signin iframe".

  • Method 2 - JavaScript:
    The following Javascript call will connect your Sign In link to the appropriate action.


    PF.loginDialog(<jquerySelector>);


JavaScript Client Objects

PF Enterprise provides a pair of JavaScript objects (PF and OrderSummary) that are available to be used in Umbraco pages and PageParts.

General Data Members

PF.user.isAuthenticated : bool
PF.user.numberOfSavedProjects : number


Order Data Members (only available in the ConfirmationExtra PagePart)

OrderSummary.confirmation : int
OrderSummary.subTotal : number
OrderSummary.discount : number
OrderSummary.tax : number
OrderSummary.shipping : number
OrderSummary.total : number
OrderSummary.balanceDue : number


Functions

PF.showError( message );
PF.blockPage( );
PF.unblockPage( );
PF.blockUI( selector );
PF.unblockUI( selector );
PF.silverlight.show( );
PF.silverlight.hide( );


jQueryUI Usage

If you plan to use jQueryUI in your Umbraco content, please note that we provide a base set of jQueryUI styles. You should plan to provide overrides for all of our default stylings. Contact us for additional details.

Tips

  • Typekit: If you use Typekit for the fonts and you can see the site make the font switch from a default to your special font, you are experiencing "FOUT" = flash of unstyled text. You can add code to the stylesheet not to load the page until the font is loaded. More info: http://help.typekit.com/customer/portal/articles/6852-controlling-the-flash-of-unstyled-text-or-fout-using-font-events
  • Put a ‘My Projects’ button in even for anonymous users. They're cookie based.  Tied to the user's browser. Just like the anonymous user's shopping cart. 
  • Use relative links. Relative links are best. If you need it to a link to a secure page like ‘checkout’ then add the class=”secure” attribute to the anchor element.  (or sign in)
  • Linking to products/groups. Use short links like shop/photo-books instead of the direct links generated from Lab 50
  • Newsletter signup.  html can’t have a <form> within a <form>. The site is already wrapped in a <form> so any others get tossed out. The submit would need to be scripted or pop something up.
  • No labels