Jump to content

dab

Members
  • Content Count

    96
  • Joined

  • Last visited

Community Reputation

31 Excellent

About dab

  • Rank
    Full Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

1,781 profile views
  1. Thanks, very good to hear of other's experiences. I looked at Snipcart, but was put off by the fees (2%/ transactions + gateway fees) just made it too expensive. Yes, back end of foxy is ugly & I needed some help with some aspects of the coding, but have found it usable for simple ecommerce projects.
  2. I've used Padloper for two Processwire sites, but not found it suitable for other projects due to only working with Paypal & Stripe payment gateways; neither being the client's gateway of choice. More recently I've used Foxycart; now on 4 ecommerce sites. I've really enjoyed the challenge integrating it into my sites with the help of some amazing Processwire forum members here 🙂 (XML & JSON datafeeds). It's compatible with over 100 payment gateways & the datafeeds can be used for updating stock levels, recording orders on to your Processwire site. I think it's worth a look if your project needs to use a specific payment gateway.
  3. dab

    ecommerce website

    Sorry for the delay getting back. Let me know which bits you need help with & I can post up some code. You can make a start with the Foxy.io code from here: https://docs.foxycart.com/v/2.0/start
  4. dab

    ecommerce website

    Snipcart looks nice (though I've not tried it). I looked at it & the 2% of transactions fees on top of payment gateway fees put me off, plus only a few payment gateways are supported. I've used Foxy.io (Foxy Cart) with ProcessWire on a site & it works really well*. Fees are low (approx £16/month) & loads of payment gateways are supported. I'm happy so post/share code if anyone needs it. *Big thanks go to both @netcarver an @Macrura for helping me with some of the datafeed integrations back to ProcessWire.
  5. I'm having problems adding a second category to check for emails & save to pages no PW errors (or php errors). On "save" no new Email Category is added. Anyone else encountering difficulties? I'm using ProcessEmailToPage v. 1.3.3, PW 3.0.123 & php PHP 7.2. Thanks Nick
  6. I used this to get the access token: https://api.instagram.com/oauth/authorize/?client_id=CLIENT-ID&redirect_uri=https://www.yourdomainhere.co.uk/processwire/module/edit?name=InstagramFeed&response_type=code 1. Replace CLIENT-ID with your own CLIENT-ID code 2. I removed the trailing slash off suggested code on Processwire Module instructions http://page.dev/processwire/module/edit?name=InstagramFeed/ Works OK for me, but I am getting error code "[InstagramFeed]: No user" too, but otherwise feed working OK.
  7. This works beautifully, thanks. & if any users need help on configuring their DNS (to point 2 domains to a single install of PW) on WHM use the >cPanel > Domains > Aliases function to add your extra domains (after enabling on > Server Configuration > Tweak Settings > Domains > "Allow users to park subdomains of the server’s hostname".
  8. @psy, thanks....so sorry...... PushAlert said I had to download the .js files. Apologies for not following the README properly - thanks for being so patient!
  9. @psy, all resolved. Now working beautifully thank you @psy! Make sure, if you recreate your website entry on the PushAlert site you download a FRESH copy of the manifest.json & sw.js (oh dear, I thought I had!). The PushAlert support team were super fast & very friendly if you run in to any problems. Thank you PushAlert.
  10. @psy, many thanks, with the latest update, I can see alerts are now being sent from Processwire to pushalert.co! Thank you 🙂🙂. My next step is to find out why push deliveries back to the subscribers are shown as "attempted" & not yet "delivered".
  11. Thanks @psy, all template files are 644 - not run in to permissions problems before. Not to worry re this one. With thanks.
  12. @psy, thanks for getting back. >field_PushAlert was not found ah yes, resolved when i used lowercase for the Pushalert field name on a later try (hope I didn't miss this instruction - sorry). >push_alert_endpoint.php template. Was this created? Yes, that was created OK. I'm thinking the lack of alerts might be PHP version related. I'll await any feedback from other users. Once again, huge thanks for all the work on the module - it's absolutely fab 🙂.
  13. @psy very excited to see this, thank you! I had a few problems, on install: /processwire/setup/field/edit?id=146 SQLSTATE[42S02]: Base table or view not found: 1146 Table mydominaname_processwire.field_PushAlert' doesn't exist (in /site/modules/PushAlert/PushAlert.module line 347) and on trying to uninstall: /processwire/module/edit?name=PushAlert&collap… Method WireFileTools::unlink does not exist or is not callable in this context (in /wire/core/Wire.php line 519) I couldn't get any notification sent on publishing a page with a FieldtypePushAlert field on it, but alerts work from the PushAlert website. Has anyone else tried & had any issues/got any pointers? I've checked modsecurity on the server & no errors & am running php 5.6.40. Thanks Nick.
  14. Sorry...this still wasn't working correctly, but this fixed it $thumb = $language->getUnformatted('flag_icon')->first; <?php foreach($languages as $language) { if(!$page->viewable($language)) continue; // is page viewable in this language? if($language->id == $user->language->id) { echo "<span class='currentlang'>"; } else { echo "<span>"; } $url = $page->localUrl($language); $hreflang = $homepage->getLanguageValue($language, 'name'); $thumb = $language->getUnformatted('flag_icon')->first; echo "<a hreflang='$hreflang' href='$url' title='$language->title'><img src='{$thumb->url}' alt='$language->title'/></a></span>"; } ?>
  15. Yes, an old post, but if you are having the same problems as @ChriWolf with the primary icon not showing when you swap to the 2nd language. It seem to fail when the field is called "language_icon", but works with the field called e.g. "flag_icon"...so omit the use of the word "language" for your image field name.
×
×
  • Create New...