Search the Community
Showing results for tags 'foxycart'.
hi all, new PW site launch: http://www.ohmspeaker.com/ some of the modules that were helpful or essential for this: cropimage formbuilder fredi importcsv minify piwik analytics procache batcher redirects version control template decorator modules manager page link abstractor sitemap xml admin custom pages markup simple navigation (for the sitemap) forum topics related to this site dev: Legacy Site URL redirects: http://processwire.com/talk/topic/3641-redirect-legacy-url-to-new-pw-page/ Clean up spelling: http://processwire.com/talk/topic/3519-use-api-to-spellcheck-whole-siteclean-up-spacing/ hashes in URLs on change selected product http://processwire.com/talk/topic/3496-help-with-url-param-change/ FormBuilder http://processwire.com/talk/topic/2904-how-to-redirect-by-id/ http://processwire.com/talk/topic/2821-3rd-party-send-conditionally/ http://processwire.com/talk/topic/2820-use-session-to-remember-form-selections/ Custom Menus http://processwire.com/talk/topic/2787-custom-menu-not-related-to-page-tree/ other notes: The skyscraper profile provided the example for how to get started with the advanced product search, a.k.a. the speaker finder. The standard search has been extended to show results in different categories. there is some use of Soma's word limiter for the news teaser text, and for making meta descriptions out of body fields, from this topic: http://processwire.com/talk/topic/3429-how-to-set-text-linecharacter-limits-in-templates/ the design is built on twitter bootstrap framework Fredi proved to be totally essential for the client, in being able to rapidly edit things without having to find things in the admin. This site is going to replace an existing site on a different domain (ohmspeakers.com). At some point we weren't sure if/how we would be able to handle the shopping cart element, and then found foxycart, which proved to be the best choice, very flexible, and easy to implement for this type of site. FC is hands down the simplest and easiest way (imho) we could achieve things like the legacy product pages, where there are various parts and upgrades displayed on 1 page. this version is sort of a "v1", and will be expanded/improved a lot for a v2, which would happen in about 4 months.. BTW - these speakers are really good; i now own 3 pairs ... they look great and do sound totally amazing...! -marc
I have two basic text fields called Product and Price. According to FoxyCart docs, I can manually create a URL as follows which will add a Picture Frame worth 100 dollars to my cart. <a href="https://YOURSTORE.foxycart.com/cart?name=PictureFrame&price=100">Add picture frame</a> Is there a way to swap out the product and price for the values in my fields? I've tried the following but it never converts my fields into actual data <a href="https://YOURSTORE.foxycart.com/cart?name=<?php echo $page->product; ?>&price=<?php echo $page->price; ?>Add picture frame</a> I There are some errors in the formatting above but you get my thinking. Typing on ipad
What is the best way of interacting with an external API within ProcessWire: (in this case it's FoxyCart but it could apply to any external API) 1. Store API data (eg customers, transactions) as pages in ProcessWire. Pros: - Can take advantage of PW's admin interface and upcoming Lister module - Better performance/user experience Cons: - Setup time. - Duplication of data (will need to have processes to keep local/remote data in sync) 2. Just pull in the data to the site through the external API as and when it's needed. Pros: - Quick setup - Data stored in one central location Cons: - Cannot use much of the in-built ProcessWire functionality for viewing/managing data. - Potential performance degradation Any thoughts are welcome