Custom Web Themes in version 3?

It used to be one would have to move custom web themes into the Aperture application bundle (Aperture.app/Contents/Resources/WebThemes). The good news is that this still works in version 3. However, it isn't pretty - is this still the only way or is there a better place now? I tried the only logical place I could think of, ~/Library/Application Support/Aperture/WebThemes, but that didn't work.

Start Firefox in [[Safe Mode]] to check if one of the add-ons is causing the problem (switch to the DEFAULT theme: Tools > Add-ons > Themes).
* Don't make any changes on the Safe mode start window.
See:
* [[Troubleshooting extensions and themes]]
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")

Similar Messages

  • Help: Custom Web Gallery Themes

    I'm currently creating web galleries for clients as I import images into Aperture, and using the "Proof" theme, but it's only available with a white background. I'd prefer a black background, but the only theme I can find is the Stock theme.
    Can I create a custom "Proof" theme with a black background and import it into Aperture?

    if you are comfortable in editing .css files ...
    all the fonts, colors, borders, etc are located within the assets folder under css ...
    if you are not comfortable ... google css and learning ...
    the W3 schools offer great CBT-DIY instruction ...
    http://www.w3schools.com/css/default.asp --- this is the css one

  • How do I get custom book themes to appear in Aperture?

    I want to create two custom book themes in Aperture - A4 Landscape and A4 Portrait - so that I can print them on A4 photo paper. However, after creating the custom themes, they do not appear in the custom theme list which is preventing me from creating an A4 sized book. I closed and restarted Aperture and I have also closed and restarted my MacBook.
    My Aperture version is 3.5.1 and I am running Mac OS X 10.9.1.
    Folders for the two custom themes I have created do appear in Users/MacPro/Library/Application Support/Aperture/Book Themes.
    Regards
    Schof

    Folders for the two custom themes I have created do appear in Users/MacPro/Library/Application Support/Aperture/Book Themes.
    Schof,
    I will try your suggestion of creating a new Aperture library and let you know what happens.
    If a new library does not fix it,  there is probably a permissions problem with your user library, or a problem with the "Books Theme" folder.
    I'd try to trash the "Books Theme" folder:
    Quit Aperture.
    Delete your "Users/MacPro/Library/Application Support/Aperture/Book Themes".
    Log off and on again.
    Create a new Custom Book.
    Can you now see it in the "Themes" drop-down menu?
    If that does not help, trash the preferences as well:
    Users/MacPro/Library/Preferences/com.apple.Aperture.plist
    and log off and on again, or restart the system.

  • Create a custom web template using VS 2012 with web features,site features sections applied

    hi,
     Want to create a  custom web template using VS 2012  in my SP 2013 environment.  i know "Vesku" has posted a great artice on this [  based on prev. version of SP].
    here -
    http://blogs.msdn.com/b/vesku/archive/2010/10/14/sharepoint-2010-and-web-templates.aspx
    i am  looking for a code based article  which has step by step process which provides how to add the site features, web features and attach the eventreceivers etc etc on sitecollection creation when i apply this template from central admin. 
    can anyone provide me any links / any source how to create a custom web template with one / two  custom features -  site features element and web features element , / master page etc ....
    I am stuck with this. as part of my reqmnt, i need to create a webtemplate with all the customlistinstances, custompagelayouts, custom masterpages, custom appln pages, custom web parts.
    help is appreciated !
    Das

    The problem is that Web Templates are deployed to a gallery in a site collection and aren't available in Central Admin when creating a new site collection.  YOu have to create the site collection without choosing a template and then choose your web
    template when you first access the root site in the site collection.  Here's an article that discusses that process here:
    http://sharepointchick.com/archive/2011/02/10/using-web-templates-to-create-site-collections.aspx
    Other than that Vesa's article is still the best one and works essentially the same in 2013 as it does in 2010.
    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

  • Is it possible to leverage InDesign Server templates in a custom web app?

    Hi there,
    I am building a custom web app and was hoping to leverage our existing InDesign Server templates within our web app. What I would like to do, is based on user input, show my template with the user's input in the browser. I have looked through the API guides for InDesign Server CS6, but I haven't been able to conclusively find anything that will allow me to use the APIs to call the server, send the data points the template requires, and then get an image back from the server.
    I believe this is possible, I am just not sure how to achieve it! Any ideas or articles that help push me in the right direction would be extremely helpful!
    Thank you!
    Marshall

    Yes it's completely possible. There are two parts to making something like this work:
    1. The scripts themselves. You can generally script InDesign Server and desktop InDesign exactly the way using ExtendScript. So that's the part of the process where your script receives variables and passes them into the template and replaces something you've identified as variable, whether text or an image or something else (perhaps a color theme, etc.). You should get your scripts running on desktop before playing around with server.
    2. The messaging between your web app and the server. Whatever language you are using (i.e. PHP, .Net, Java, Ruby…) there is a way to make a SOAP call to InDesign Server to tell it basically "run this script with these parameters". You should get the "hello world" script running from a SOAP call on the server before using your real variable-driven document.
    The documentation of these things is available here:
    http://www.adobe.com/devnet/indesign/sdk.html
    You need to download the InDesign Server SDK (don't worry if you're on CC and it says CS6, almost nothing changed) and the InDesign Scripting SDK. The Server SDK deals with part #2 above, the Scripting SDK with part #1.
    It really isn't that hard. I should warn you, though, that it is addictive and once you do your first one you will become all-powerful and want to do nothing else. :-)
    Good luck and don't hesitate to ask questions.
    Max
    http://blog.siliconpublishing.com

  • Exchange 2013 SP1 & Custom OWA Theme

    On Friday of last week we updated from Exchange 2013 CU2 to Exchange 2013 SP1. Since updating our custom OWA theme no longer works. We configured it according to the following guide:
    http://technet.microsoft.com/en-us/library/bb201700(v=exchg.150).aspx
    The theme we customized was stored in the following location:
    \Client Access\OWA\version\Owa2\resources\themes\"title of our theme"
    Themes no longer appear to be stored in this location and I am uncertain as to where they have moved and how to apply them. Has anyone else run into this issue?

    Hi,
    Can we try to re-importing the theme again?
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Export to PDF in Sharepoint Custom web part.

    Hi,
    I want to export my page to pdf in sharepoint custm web part. I am using below code to export to pdf. when i click the export button i am getting below
    Error. how to resolve this error? pLease help me.
    Code
    protected void ExporttoPDF_Click(object sender, EventArgs e)
                Response.ContentType = "application/pdf";
                Response.AddHeader("content-disposition", "attachment;filename=ExporttoPDF.pdf");
                Response.Cache.SetCacheability(HttpCacheability.NoCache);
                StringWriter sw = new StringWriter();
                HtmlTextWriter hw = new HtmlTextWriter(sw);
                this.Page.RenderControl(hw);
                StringReader sr = new StringReader(sw.ToString());
                Document pdfDoc = new Document(PageSize.A4, 10f, 10f, 100f, 0f);
                HTMLWorker htmlparser = new HTMLWorker(pdfDoc);
                PdfWriter.GetInstance(pdfDoc, Response.OutputStream);
                pdfDoc.Open();
                htmlparser.Parse(sr);
                pdfDoc.Close();
                Response.Write(pdfDoc);
                Response.End();
    Error 
    Server Error in '/' Application.
    RegisterForEventValidation can only be called during Render();
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
    Exception Details: System.InvalidOperationException: RegisterForEventValidation can only be called during Render();
    Source Error:
    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
    Stack Trace:
    [InvalidOperationException: RegisterForEventValidation can only be called during Render();]
       System.Web.UI.ClientScriptManager.RegisterForEventValidation(String uniqueId, String argument) +11081278
       System.Web.UI.WebControls.TextBox.AddAttributesToRender(HtmlTextWriter writer) +455
       System.Web.UI.WebControls.WebControl.RenderBeginTag(HtmlTextWriter writer) +27
       System.Web.UI.WebControls.TextBox.Render(HtmlTextWriter writer) +27
       System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +240
       System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer) +42
       System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +240
       System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +240
       System.Web.UI.HtmlControls.HtmlForm.RenderChildren(HtmlTextWriter writer) +411
       System.Web.UI.HtmlControls.HtmlForm.Render(HtmlTextWriter output) +87
       System.Web.UI.HtmlControls.HtmlForm.RenderControl(HtmlTextWriter writer) +53
       System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +240
       System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer) +42
       System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +240
       System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +240
       System.Web.UI.Page.Render(HtmlTextWriter writer) +38
       Microsoft.SharePoint.WebPartPages.WikiEditPage.Render(HtmlTextWriter writer) +207
       PayrollProject.PaySlip4Employee.PaySlip4EmployeeUserControl.btnPDF_Click(Object sender, EventArgs e) +425
       System.Web.UI.WebControls.Button.OnClick(EventArgs e) +115
       System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +140
       System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +29
       System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2981
    Version Information: Microsoft .NET Framework Version:2.0.50727.5472; ASP.NET Version:2.0.50727.5474 

    Hi,
    We know that the Page.EnableEventValidation property is set to true(The default is true.),  Sharepoint Custom web(ASP.NET Web) validates that a control event originated from the user interface that was rendered by that control. A control registers its
    events during rendering and then validates the events during postback or callback handling.
    If you write client script freely,you might have to set "EnableEventValidation = false" in your C# code behind,but this method may be troublesome in SharePoint,
     so the method of "sadomovalex"( http://sadomovalex.blogspot.in/) is a good idea.
    Best Regards

  • Is it possible to transfer custom web galleries from CS3 to CS5?

    Does anyone know if it is possible to transfer my custom web galleries from PS CS3 to Adobe Bridge CS5?

    Collections are not a physical directory.  It is kind of like a spreadsheet that tells Bridge where to find the pictures and display them, so you can't just move the folder.
    Smart collections are a little easier to transfer, but do not think CS3 had those.
    Not an expert here but believe you would first have to have the same computer  and HD so that all the picture loacations are the same.
    Then go to User/App Data/Roaming/Adobe/Bridge/Collections and copy file from CS3 and insert into same spot for CS5.
    Maybe someone that have done this will jump in and prove me wrong.

  • Help needed with Custom Web ADI Integrator for Mail Merge

    Hello,
    I've created a custom web adi integrator to generate letters to advise of end of probationary periods.
    The problem is that at the end of the process when the letter is opened in Word 2007, it only displays one record, and does not allow me to "preview results" and cycle through the records (this part is greyed out). It appears that the letter is not merged with the data spreadsheet although it does display one record from it.
    Our EBS version is 12.1.3 and we are using Office 2007.
    These are the steps I have followed so far (in brief):
    - Create a view to provide data (names, addresses etc).
    - Set up a new custom function (similar to seeded function HR Integrator Setup).
    - Add the custom function and other functions to Desktop Integration responsibility.
    - Add the relevant functions to end user's responsibility menu.
    - Add new category "other" to HR_ADI_DOCUMENT_TYPE lookup.
    - Create Download Excel Integrator by choosing Desktop Integration -> HR Integrator Setup. Enter "PER" for application and my view for the View Name. Upload.
    - Create another Excel document by choosing Desktop Integration -> HR Maintain Form Function Associations, and choose the integrator created above. Enter my custom function name in the generated spreadsheet and upload.
    - Define a layout for the new integrator.
    - Run the integrator under the end user responsibility and save the resulting spreadsheet, which is full of data as expected.
    - Create the letter in Word, using the saved spreadsheet as the data source for the merge. At this point the merge is successful.
    - Go to Desktop Integration -> Document Management and upload the Word mail merge document. Associate it with the custom document type created earlier.
    - Link this document to my integrator.
    - Go in as end user responsibility and run the integrator.
    At this point after enabling macros it loads 2 spreadsheets (one full of data) and the Word document, but the Word document only displays one record (approx the 10th in the list - there are about 100 in total). All of the relevant merge-related menu items on the "Mailings" tab are greyed out.
    Can anyone offer any pointers please?
    I did wonder whether it mattered if I changed the names of documents, e.g when I download and save the resulting spreadsheet full of data which I then use to merge to in the Word Doc, is it OK to call the spreadsheet anything or should it be left as the default name?
    Many thanks,
    Hazel

    Hi Nandhakumar.P,
    thanks for your response. Please find the answers below:
    - Set up a new custom function (similar to seeded function HR Integrator Setup).
    System Administrator -> Application -> Function. Query back the seeded User Function Name = "HR Integrator Setup", make a note of the details, then add a custom function entitled "NTC_HR_LETTERS" with the same details.
    - Add the custom function and other functions to Desktop Integration responsibility.
    System Administrator -> Application -> Menu. Query back User Menu Name = "Desktop Integration Menu" and add the following functions:
    WITHOUT PROMPT
    a. HR Integrator Setup
    b. HR Maintain Integrator Form Functions
    c. HR Disable Integrator
    d. HR ADI Document Overwrite Page
    e. HR ADI Document Upload Page
    f. The custom function created in previous step ("NTC_HR_LETTERS")
    WITH PROMPT
    g. HR ADI Document Management Page
    - Add the relevant functions to end user's responsibility menu.
    System Administrator -> Application -> Menu. Query back menu attached to custom responsibility of end user that will perform the action once set up.
    Add the following:
    a. The custom function "NTC_HR_LETTERS" as created previously (without prompt)
    b. Desktop Integration - Create Document (With Prompt. This function will be used to generate letters)
    - Add new category "other" to HR_ADI_DOCUMENT_TYPE lookup.
    SA_Application Developer -> Application -> Lookups -> Common. Query back Type = HR_ADI_DOCUMENT_TYPE and add a new entry entitled "Other". This document type is later assigned to the Word document I upload and link to the integrator.
    I hopoe that answers your questions.
    Regards,
    Hazel

  • Deciphering Aperture Web Themes: the html templates v3

    version 3 of my Aperture Web Theme html template reference. enjoy
    the html templates.
    rkid attributes:
    Aperture uses proprietary ids within the html documents to identify the parts it needs to play with. These ids are 'rkid' ids. for example,
      <ul id="nav" rkid="navbar">
    These are the rkid values that I've identified so far:
      "navbar"
        a <ul> element containing all of the navigation elements.
      "active" and "inactive"
        rkid attributes to enable the coder to place different formatting on
        current and non-current page numbers in the navbar.
        eg; <li rkid="active"><span class="currentPage">PageNumber</span></li>
          <li rkid="inactive"><a href="IndexPageURL_">_PageNumber</a></li>
      "content"
        a <div> containing all of the album images and their metadata.
      "pictureblock"
        a mandatory <table> in which the images are placed, one image per <td>.
        the <table> must even be used on the Detail page where only one image is
        displayed.
        the metadata will be within the "pictureblock" table if more than one
        image is displayed so that the metadata can be tied to the image. if
        only one image is displayed; i.e., the Detail page; the metadata may be
        in a <td> outside of the table that the image is in but still within the
        "content" div, usually in the following format:
          <div rkid="content">
            <table>
              <td>metadata
              <td><table rkid="pictureblock">
      "image"
        the rkid for the <img> elements containing the album images, frequently
        placed in <dt> elements within the table's cells.
      "metadata" (added in Decipher v3)
        all metadata for the respective image is specified within this element.
        everything within the element is repeated for every metadata value.
        the Aperture themes use the <ul> element but <div> also works:
          <div rkid="metadata"><p>metaname: metavalue</p></div>
      "titleblock"
        a <div> containing the title text; usually <h3>; for Journals. the <h3>
        element within this element must be given the attribute rkid="text" or
        Aperture will ignore it.
      "textblock"
        a <div> containing the description text for Journals. as with the
        titleblock, the <p> element/s within this div must be given the
        attribute rkid="text".
      "text"
        the rkid given to the text data within the titleblock and textblock
        elements.
    Place holders:
      PageTitle
        used in the <head> of the html. it's made up of the Album/Journal's name plus a page number. eg; "My lucky album - Page 1".
      IndexPageURL
        the gallery page/s URLs; may be more than one.
      ThumbImageURL
        the href links for the images, whether thumbnails or detail full size.
      DetailPageURL
      used within navbar:
        PageCount
        PageNumber
        PreviousPageNumber
        PreviousPageURL
        NextPageNumber
        NextPageURL
        PageCount the total number of pages
        PageNumber includes all of the page numbers listed in the navbar, one
          occurrence for each page.
        _Previous and _Next are more specific and are currently used to draw the
          prev/next arrows in the navbar.
      ImageName
      ImageNameSpace
      PlateNameSpace
      PlateNumberSpaceSlash
        *only seen* when 'Enable Plate Metadata' option in the tag popup menu is
          chosen.
        used to represent an index of the image in the album. the first image
          shown gets the index 1, the second 2 and so on.
        for the Image placeholders, the word 'Image' is used.
        for the Plate placeholders, the word 'Plate' is used.
        space indicates an extra space after the index, probably for html
          formatting purposes because it's only used within <dt> elements.
        slash indicates an extra / character after the index.
        examples:
          ImageName > 'Image 1'.
          ImageNameSpace > 'Image 1 '.
          PlateNameSpace > 'Plate 1 '.
          PlateNumberSpaceSlash > '1 / '.
      metaname
      metavalue
        the placeholders for all of the metadata names/values in the selected
        metadata set.
      PageWidth
        not sure if Aperture calculates it based on the width and number of
        images being displayed in both gallery and detail pages.
        don't know why it's only used in the Special Occasion theme.
      CellWidth
        the width of the table cells containing the album images. not
        necessarily the width of the images. may include margins as specified in
        the albuminfo.plist files.
      ImageWidth
        the width of the image.
      TableWidth
        the width of the pictureblock table. it can probably be applied to other
        elements too but it's length is almost certainly calculated from the
        pictureblock table.
    Operative attributes:
      removeonfirstpage="yes"
        used in the navbar to remove the Prev link from the first page.
        because it's applied to the <a> element, the <a> element is removed
          while leaving an empty <li> in place.
      removeonlastpage="yes"
        used in the navbar to remove the Next link from the last page.
        because it's applied to the <a> element, the <a> element is removed
          while leaving an empty <li> in place.
      removeonsinglepage="yes"
        used in the navbar to remove elements when there's only one page.
        used in a <div> in the Art Collection to remove the whole navbar on
        single pages.
      contenteditable="yes"
        used in text elements to indicate that the user can customise the text.
        not necessary in titleblock and textblock rkid="text" elements.
        in elements outside of the titleblock and textblock elements, content
        will not be truly editable unless a textid is assigned to the text
        elements. unfortunately, all text elements with textids are always
        'common' and can not be specific to any one image.
      common="yes"
        the element is seen on all pages.
    Other attributes:
      metaseparator="|"
        used in metadata formatting, within the metadata lists.
        you can add additional characters. for example, the metaseparator
        in the Stock Black theme is " | "; ie, a | bar with a space on both
        sides. (Decipher v3)
        if the metaseparator is specified and the html template places the
        metadata into <li> elements as it does in most of the current themes,
        then it produces non-standard html code with the metaseparator between
        concurrent <li> elements.
      metalayout="paragraph"
        used in metadata formatting, within the metadata lists.
        if not specified, the metadata will not be exported. (Decipher v3)
      singlenesting="yes"
        used in metadata formatting. not sure what it does yet.
      textid="x"
        used to id text elements outside of the titleblock and textblock
        elements.
        possibly no limit to the number and id names used.
        examples used:
          textid="copyright"
          textid="header1"
      picturename="x"
      pictureimage="true"
        picturename gives the image an id.
        pictureimage="true" tells Aperture that the image is a static image
        which can be designated by the user during setup of the album. they show
        up in Aperture as grey blank rectangles with cross-eyes in the middle.
        they do not need to be inside the "content" element
        with picturename and pictureimage, we can place as many static images on
        the page as we wish.
    Assertions:
      Aperture uses the rkid values to identify the areas of the html to be
      repeated for the respective objects.
      standard id and class attributes are only used by the css for formatting and
      not by Aperture to write the html data.
    Notes:
      Aperture is hardcoded to expect and require that the album images are always
      within a <table rkid="pictureblock"> element. it is not possible to place
      album images outside of the table. all album images must be placed within
      <td> cells within the table. the <td> code is repeated for each image.
      image metadata is also normally within the rkid="content" element although
      it can be outside of the rkid="pictureblock" element.
      by default, the textblock rkid="text" element is added when the T+ button is
      pressed within Aperture. the textblock element is switched with the
      titleblock element when the Title/Text toggle button is clicked.
      width and height attributes of <img> elements are rewritten by Aperture
      based on the inserted images. placeholders aren't necessary within <img>
      elements.
      comments are stripped from the html before export some but some
      Aperture-proprietary attributes are forgotten and left behind.
      some pages use the html 4.0 loose doctype. others use the xhtml 1.0 strict
      doctype.
      all markup is converted and exported in UPPER-CASE. personally, I prefer
      lower-case.
      high-ascii characters entered by the user are not converted to their html
      entities when available. eg, the © character.
      multiple <p> elements can be inserted into the titleblock and textblock
      <div> elements but each of them must have the rkid="text" attribute. any
      element without this attribute will be ommitted by Aperture.
      the reason there are Smart Galleries but no Smart Journals is because you
      need to write text between each row of images.
      titleblock and textblock elements will not be applied to Galleries or Detail
      templates; only to Journals.
      if there are more than one titleblock or more than one textblock, only the
      first will be used by Aperture.
      upon export, Aperture will remove everything from within the rkid="content"
      element which is not the pictureblock, titleblock or textblock elements.
      (Decipher v3)
      some of the Aperture templates have xhtml doctypes but are exported from
      Aperture with html 4.0 loose doctypes. weird! worthy of note is the fact
      that UPPER-CASE element names is not permitted with xhtml which is
      case-sensitive. (Decipher v3)
    Questions:
      are there variable scopes with each rkid? eg, within the "content" rkid, can
      every variable/placeholder be accessed?
      why did the Aperture team use Definition List <dl>, <dt>, <dd> elements for
      the images and related metadata in the table? easier css formatting?
    JavaScript: (Decipher v3)
      you can include JavaScript in the html code but cannot wrap it in html
      comments because Aperture will remove everything within comments.
      Aperture variables such as PageNumber will not be replaced within
      attributes such as <body onload="dialog(PageNumber);">.
      it is very difficult to use document.write anywhere within the html <body>.
      Aperture seems to be using JavaScript to export the html and its code is not
      able to cope with more than one instance of document.write in the html
      templates. after hours of trial and error, I found that the most stable way
      to use JavaScript within the html <body> was to only use one <script>
      element and place everything within it. using document.write within a second
      <script> element would almost certainly lead to unpredictable exported html,
      and instability and crashes in Aperture.
    iMac Duo Core 2GHz 2GB   Mac OS X (10.4.6)  

    It worked. I still have a few tweaks to do on my final template, but the method I described above works. I've set up my templates like this:
    1) one large image per thumbnail page (like a photo essay or photo blog style)
    2) same size image on detail page, but with paypal buttons directly below in their own table (I have several different paypal buttons - for different print sizes and a couple other things like postcards, etc.)
    The neatest thing about this setup is that since it's all controlled by flat html and css, it looks almost like javascript the way the paypal buttons pop up - the image stays in exactly the same place and the buttons just appear below it (haven't tried it on a slow connection, though, probably a slight delay).
    This is great because I hate javascript but sometimes like the immediate visual effects it allows.
    This template makes it trivial to create a reverse chronological gallery/journal - kind of like a photoblog - and allows visitors to view the large images without the extra clutter of the buttons, but then they can just click on the image to reveal the buttons and click the image again to hide them.
    The benefit of putting these buttons directly into the Aperture templates rather than using a find-replace script to add them to iWeb pages after processing? Well, using Aperture, I can add the PageTitle tag to the Paypal button - it doesn't work in hidden form fields or anything that needs to go inside an attribute, but it does parse using a textarea field, which I hid with CSS - This alleviates the problem many photographer sites have where they ask the buyer to email them with the image name/number they want - this way, the shopping cart automatically knows which image they're ordering.
    PageTitle uses the following format: Gallery/Journal Name - Image/Version Name
    So using this tag in the Paypal button tells me which image the buyer wants and which gallery they were viewing when they ordered - simple but effective.
    Anyway, I know it's been a few weeks since I last replied, but I thought I would post this for others who might be interested in doing something similar - entirely through Aperture. Sorry about the run-on sentences; I'm a bit pre-occupied to proofread today.

  • Deciphering web themes: the html templates; expanded reference.

    the html templates.
    RKID attributes:
    Aperture uses proprietary ids within the html documents to identify the parts it needs to play with. These ids are 'rkid' ids. for example,
       <ul id="nav" rkid="navbar">
    These are the rkid values that I've identified so far:
       "navbar"
          a <ul> element containing all of the navigation elements.
       "active" and "inactive"
          rkid attributes to enable the coder to place different formatting on
          current and non-current page numbers in the navbar.
          eg; <li rkid="active"><span class="currentPage">PageNumber</span></li>
             <li rkid="inactive"><a href="IndexPageURL_">_PageNumber</a></li>
       "content"
          a <div> containing all of the album images and their metadata.
       "pictureblock"
          a mandatory <table> in which the images are placed, one image per <td>.
          the <table> must even be used on the Detail page where only one image is
          displayed.
          the metadata will be within the "pictureblock" table if more than one
          image is displayed so that the metadata can be tied to the image. if
          only one image is displayed; i.e., the Detail page; the metadata may be
          in a <td> outside of the table that the image is in but still within the
          "pictureblock" table, usually in the following format:
             <div rkid="content">
                <table>
                   <td>metadata
                   <td><table rkid="pictureblock">
       "image"
          the rkid for the <img> elements containing the album images, frequently
          placed in <dt> elements within the table's cells.
       "titleblock"
          a <div> containing the title text; usually <h3>; for Journals. the <h3>
          element within this element must be given the attribute rkid="text" or
          Aperture will ignore it.
       "textblock"
          a <div> containing the description text for Journals. as with the
          titleblock, the <p> element/s within this div must be given the
          attribute rkid="text".
       "text"
          the rkid given to the text data within the titleblock and textblock
          elements.
    Place holders:
       PageTitle
          used in the <head> of the html. it's made up of the Album/Journal's name plus a page number. eg; "My lucky album - Page 1".
       IndexPageURL
          the gallery page/s URLs; may be more than one.
       ThumbImageURL
          the href links for the images, whether thumbnails or detail full size.
       DetailPageURL
       used within navbar:
          PageCount
          PageNumber
          PreviousPageNumber
          PreviousPageURL
          NextPageNumber
          NextPageURL
          PageCount the total number of pages
          PageNumber includes all of the page numbers listed in the navbar, one
             occurrence for each page.
          _Previous and _Next are more specific and are currently used to draw the
             prev/next arrows in the navbar.
       ImageName
       ImageNameSpace
       PlateNameSpace
       PlateNumberSpaceSlash
          *only seen* when 'Enable Plate Metadata' option in the tag popup menu is
             chosen.
          used to represent an index of the image in the album. the first image
             shown gets the index 1, the second 2 and so on.
          for the Image placeholders, the word 'Image' is used.
          for the Plate placeholders, the word 'Plate' is used.
          space indicates an extra space after the index, probably for html
             formatting purposes because it's only used within <dt> elements.
          slash indicates an extra / character after the index.
          examples:
             ImageName > 'Image 1'.
             ImageNameSpace > 'Image 1 '.
             PlateNameSpace > 'Plate 1 '.
             PlateNumberSpaceSlash > '1 / '.
       metaname
       metavalue
          the placeholders for all of the metadata names/values in the selected
          metadata set.
       PageWidth
          not sure if Aperture calculates it based on the width and number of
          images being displayed in both gallery and detail pages.
          don't know why it's only used in the Special Occasion theme.
       CellWidth
          the width of the table cells containing the album images. not
          necessarily the width of the images. may include margins as specified in
          the albuminfo.plist files.
       ImageWidth
          the width of the image.
       TableWidth
          the width of the pictureblock table. it can probably be applied to other
          elements too but it's length is almost certainly calculated from the
          pictureblock table.
    Operative attributes:
       removeonfirstpage="yes"
          used in the navbar to remove the Prev link from the first page.
          because it's applied to the <a> element, the <a> element is removed
             while leaving an empty <li> in place.
       removeonlastpage="yes"
          used in the navbar to remove the Next link from the last page.
          because it's applied to the <a> element, the <a> element is removed
             while leaving an empty <li> in place.
       removeonsinglepage="yes"
          used in the navbar to remove elements when there's only one page.
          used in a <div> in the Art Collection to remove the whole navbar on
          single pages.
       contenteditable="yes"
          used in text elements to indicate that the user can customise the text.
          not necessary in titleblock and textblock rkid="text" elements.
       common="yes"
          the element is seen on all pages.
    Other attributes:
       metaseparator="|"
          used in metadata formatting, within the metadata lists.
       metalayout="paragraph"
          used in metadata formatting, within the metadata lists.
       singlenesting="yes"
          used in metadata formatting. not sure what it does yet.
       textid="x"
          used to id text elements outside of the titleblock and textblock
          elements.
          possibly no limit to the number and id names used.
          examples used:
             textid="copyright"
             textid="header1"
       picturename="x"
       pictureimage="true"
          picturename gives the image an id.
          pictureimage="true" tells Aperture that the image is a static image
          which can be designated by the user during setup of the album. they show
          up in Aperture as grey blank rectangles with cross-eyes in the middle.
          they do not need to be inside the "content" element
          with picturename and pictureimage, we can place as many static images on
          the page as we wish.
    Assertions:
       Aperture uses the rkid values to identify the areas of the html to be
       repeated for the respective objects.
       standard id and class attributes are only used by the css for formatting and
       not by Aperture to write the html data.
    Notes:
       Aperture is hardcoded to expect and require that the album images are always
       within a <table rkid="pictureblock"> element. it is not possible to place
       album images outside of the table. all album images must be placed within
       <td> cells within the table. the <td> code is repeated for each image.
       image metadata is also normally within the rkid="content" element although
       it can be outside of the rkid="pictureblock" element.
       by default, the textblock rkid="text" element is added when the T+ button is
       pressed within Aperture. the textblock element is switched with the
       titleblock element when the Title/Text toggle button is clicked.
       width and height attributes of <img> elements are rewritten by Aperture
       based on the inserted images. placeholders aren't necessary within <img>
       elements.
       comments are stripped from the html before export some but some
       Aperture-proprietary attributes are forgotten and left behind.
       some pages use the html 4.0 loose doctype. others use the xhtml 1.0 strict
       doctype.
       all markup is converted and exported in UPPER-CASE. personally, I prefer
       lower-case.
       high-ascii characters entered by the user are not converted to their html
       entities when available. eg, the © character.
       multiple <p> elements can be inserted into the titleblock and textblock
       <div> elements but each of them must have the rkid="text" attribute. any
       element without this attribute will be ommitted by Aperture.
       the reason there are Smart Galleries but no Smart Journals is because you
       need to write text between each row of images.
       titleblock and textblock elements will not be applied to Galleries or Detail
       templates; only to Journals.
       if there are more than one titleblock or more than one textblock, only the
       first will be used by Aperture.
    Questions:
       are there variable scopes with each rkid? eg, within the "content" rkid, can
       every variable/placeholder be accessed?
       why did the Aperture team use Definition List <dl>, <dt>, <dd> elements for
       the images and related metadata in the table? easier css formatting?
    iMac Duo Core 2GHz 2GB   Mac OS X (10.4.6)  

    IMPORTANT!
    An updated version is available in thread:
    Deciphering Aperture Web Themes: the html templates v3.

  • User defined custom Windows theme is not saved during roaming profile syncronization

    Hi,
    We have Windows 8.1 computers in a 2012 domain. The user profiles is roamed to a file server during logon and logoff.
    We have excluded many folders under appdata\roaming and appdata\local and was also excluding \AppData\Roaming\Microsoft\Windows\Themes, but included this folder again in the roaming profile.
    Our problem is that the users is saving a custom Windows theme, but when logging out and in again the settings is still there, but after a while the custom color settings set back to Windows defaults.
    We are using VMware View 5.3 and are using non-persistent pools, this means that the users get a new "computer" every time they login and at logoff the computer is reset/revert to default snapshot and given to another user.
    Therefore most of the settings under Local appdata and all localow appdata files and configurations is reset at logoff for users.
    what is the required files/folders/registry keys to fully support custom Windows themes ? If we have that info we can include the necessary files in our user enviroment.
    we have not found any userful info on the web for this specific issue.

    Hi,
    In my opinion, you can try to create a new Default User Profile on this system and mondify its defualt theme as you want. Because everytime new user login, it would generate the new user profile based on Default User Profile.
    You can refer to the content below for more details:
    Customize the default local user profile when preparing an image of Windows:
    https://support.microsoft.com/en-us/kb/973289
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Yes, I we have already made a custom theme on the image, but in this case we need to configure a special theme for one specific user during logon. 
    Does anyone know of a solution to this?  

  • 2013 Custom Web Parts in Page Layouts not showing for users

    Custom Web Parts in Page Layouts not showing for users
    I have created a master page in the root site collection for a subsite I am developing. I created content types and custom page layouts for the pages within the subsite.
    I used the snippet tool in the design manager to create web parts and page field markup which I copied into the custom layout HTML pages in the root site collection. For instance I have an image viewer web part that I place there to serve as a section title.
    The problem is that I can see all these customer layout page parts no problem but my users cannot. This leads me to believe its permissions, I am site owner of both the subsite and root site collection.
    The users that cannot see the web parts are site members of the site and restricted read users on the root site collection (where the layouts are stored).
    What gives I'm finding it hard to understand why a snipet generated web part wouldn't show in all pages created from that layout page.
    Any help would be appreciated, Havent found anything on this issue online. weird.

    It is a permission issue indeed. Fix is simple, make sure you check out the page layout page, then check it back in as published version.
    John Architect

  • Custom web service in SharePoint 2010

    Hi,
    I have developed one custom web service and deployed in inside 14 hive Layout folder. I have to consume this custom web service in WCF REST services. This WCF REST service will be consumed in to HTML 5 and javascript application (Presentation Layer). Here
    is the code for Custom web service :
    [WebMethod]
    public string[] GetSponsorList()
    string url = "https://ptmdev.bpiper.com/";
    //string strUserName = "ravikant";
    string sponsorTitle = string.Empty;
    string[] arrTitle;
    string[] myArray;
    DataTable dtSponsor = new DataTable();
    string error = string.Empty;
    ArrayList myArrayList = new ArrayList();
    try
    dtSponsor.Columns.Add(new DataColumn("sValue", typeof(string)));
    dtSponsor.Columns.Add(new DataColumn("sText", typeof(string)));
    using (SPSite site = new SPSite(url))
    using (SPWeb web = site.OpenWeb())
    //SPUserToken userToken = web.AllUsers[strUserName].UserToken;
    SPWebApplication webApplication = SPContext.GetContext(web).Site.WebApplication;
    SPSiteCollection siteCollections = webApplication.Sites;
    int i = 0;
    if(web.CurrentUser!=null)
    myArrayList.Add("User:"+web.CurrentUser.LoginName);
    else
    myArrayList.Add("Null User..");
    foreach (SPSite siteCollection in siteCollections)
    if (siteCollection.RootWeb.DoesUserHavePermissions(SPBasePermissions.ViewPages))
    if (siteCollection.Url.ToString().ToLower().Contains("/sponsor/"))
    sponsorTitle = siteCollection.RootWeb.Title;
    if (string.IsNullOrEmpty(sponsorTitle))
    arrTitle = siteCollection.Url.Split('/');
    sponsorTitle = arrTitle[arrTitle.Length - 1];
    dtSponsor.Rows.Add(new object[] { siteCollection.Url, sponsorTitle });
    i = i + 1;
    siteCollection.Close();
    catch (Exception ex)
    error = ex.Message;
    myArrayList.Add(error);
    if (dtSponsor.Rows.Count == 0)
    myArrayList.Add("No Data available 101");
    myArrayList.Add("No Data available 102");
    myArrayList.Add("No Data available 103");
    for (int i = 0; i <= dtSponsor.Rows.Count - 1; i++)
    for (int j = 0; j <= dtSponsor.Columns.Count - 1; j++)
    myArrayList.Add(dtSponsor.Rows[i][j].ToString());
    myArray = (string[])myArrayList.ToArray(typeof(string));
    return myArray;
    Above code will return a string array of SiteCollection URLs and Title. Th issue is siteCollection.RootWeb.DoesUserHavePermissions(SPBasePermissions.ViewPages)
    logic is failed and due to this string array does not return desired result.
    web object is not containing users information due to that DoesUserHavePermissions logic is
    failing.
    Urgent help is needed.
    Thanks,
    Ravi

    Hi,
    According to your post, my understanding is that you have issue about siteCollection.RootWeb.DoesUserHavePermissions(SPBasePermissions.ViewPages) logic when you custom web service.
    You can use siteCollection.RootWeb.DoesUserHavePermissions( SPContext.Current.Web.CurrentUser, SPBasePermissions.ViewPages)
     to check whether it works.
    In addition, you can use a RunWithElevatedPrivileges delegate.
    For more information, you can refer to:
    “Attempted to perform an unauthorized operation” and SPWeb.DoesUseHavePermissions
    Thanks,
    Linda Li                
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Linda Li
    TechNet Community Support

  • Parameter passing for custom web service reports

    <p>Hi,</p><p>I created a report file and published it as a .Net web service. I was able to set the web service to a report viewer in my windows application. I am using Crystal Reports Version 11 R2 and Visual Studio 2005 for my development.</p><font size="2" color="#008080">ReportWebService</font><font size="2"> service = </font><font size="2" color="#0000ff">new</font><font size="2"> </font><font size="2" color="#008080">ReportWebService</font><font size="2">(); </font><font size="2"><p>crystalReportViewer1.ReportSource = service;</p></font><p>Now, my question is how do I pass a parameter from the windows application to the custom report web service. It does not seem to accept any paramters through constructors or other custom web methods.</p><p>If I need to change my design or approach, I am welcome to that as long as I am able to host the report file on a central location. The .rpt file (exposed by the web service) does not have any parameters but the data population logic inside the web service might be based on some conditions which I need to pass as parameter.</p><p>Thanks in advance.Regards, Gulzar</p>

    <p>When using a Report Web Service, you must use the Viewer&#39;s SDK to interact with the report. So in your case, if you want to pass parameters to the report, the viewer exposes a ParameterFieldInfo property that you can set. You can download samples on how to do this or check out the <a href="http://devlibrary.businessobjects.com/BusinessObjectsXIR2SP2/en/devsuite.htm" target="_blank">DevLibrary</a> for more details.</p><p>However, one of your last statements you said your report does not have any parameters but your web service does.....could you elaborate on that?  Did you modify the .asmx that is autogenerated to add/modify the web service methods?  If so, then you will not be able to pass parameters to the new/modified web service.  The autogenerated web service for the report cannot be modified in this way since the viewer is designed to use the web services methods as-is.   In other words, the viewer is the only client/consumer of the Report Web Service so any interaction you want with the report must be done through the viewer, if the viewer exposes the functionality.  </p><p>In general, because the viewer is the only supported consumer of the Report Web Service, there are many limitations to interacting with the report.  Depending on how much control you want over the report at runtime, you may not want to use Report Web Services.  If you want to centralize reports for a Windows application, your best option is to load the reports from a network share using a UNC path when loading the report.  Of course, this assumes your application is running from some kind of internal network.  Any other kind of solution to centralized reports would require a web-based solution.</p><p>If you must use a Windows application, then you could host a IE control on your form that accesses a web page that displays reports but then you would have to develop and support a web application in addition to your windows application.  It&#39;s not the best solution but it&#39;s an option!  :-)</p><p>-MJ</p>

Maybe you are looking for