On Oct 18, 12:27 am, "Pete Kucera" <[EMAIL PROTECTED]> wrote: > I was able to successfully integrate the farcryblog into my shared hosting > FarCry installation. Albiet, I needed to make a few small changes to the > location of and reference to the webskins. For some reason, FarCry could > not locate the webskins in the farcryblog plugin directory. I copied the > farBlogPost folder into the webskins folder under projects/myprojectname and > it works.
This may work but is not recommended. To pick up the farblogpost webskins make sure you: - reinitialise the application properly (eg. ?updateapp=1) - have the plugin list in your ../www/farcryconstructor.cfm in the right order ie. farcryblog must be loaded before skins Webskins are loaded in the following order: - core - the plugin list - your project If you have identical webskins, then the last webskin to be loaded is the one used. This is pretty cool, and i think unique amongst frameworks. It means you can have a plugin like farcryblog just work, then override it with another plugin such as a "skin" and then in turn override that in your project (the ultimate arbitrator of what happens in your application instance). > There is one other item to note for those of you strugging with custom > webskins not showing up in the farcryblog. The standard webskin prefix as > per FarCry documentation for display pages is displayPagexxx where the 'xxx' > is your added custom webskin name. You may have noticed webskin names such > as 'displayPageStandard, displayPageHome, etc. > > When creating or modifying a custom types .cfc, the <cfproperty/> tag that > creates the webskin dropdown can specify the prefix for which webskins will > be 'called' from your directory into your content form. The prefix > (ftPrefix attribute) specified in the farcryblog plugin contains the value > 'displayPageStandard'. So, as I created webskins called displayPagexxx they > were not being included. They wouldn't be included unless I named them > displayPageStandardxxx. To remedy this problem, I simply changed the > ftPrefix value for that property to 'displayPage' and now my webskins appear > in the drop down on the content form. Good catch! This is definitely not the intended behaviour. Your correction is spot on. http://bugs.farcrycms.org/browse/FCB-28 > p.s. So far, I really like this FarCry application framework. Once you get > to understand how it thinks, its potential becomes evident. Thanks to all > those to created it and to those who keep it alive! Thanks for the kind words. It's somewhat of a "best kept secret" in the CF community ;) We're going to make an effort in coming months to spread the FarCry message. Best regards, geoff http://www.daemon.com.au/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "farcry-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/farcry-dev?hl=en -~----------~----~----~----~------~----~------~--~---
