Jump to content

gmclelland

Members
  • Content Count

    480
  • Joined

  • Last visited

  • Days Won

    2

gmclelland last won the day on July 23

gmclelland had the most liked content!

Community Reputation

379 Excellent

About gmclelland

  • Rank
    Sr. Member

Profile Information

  • Gender
    Male
  • Location
    Texas (DFW area)

Recent Profile Visitors

3,056 profile views
  1. https://github.com/processwire/processwire-requests/issues/126
  2. Hi @Pete Would you happen to know why I can’t long press on links to topics within the forum listings on an iPad? When I try to read the Unread activity section in the forum, I like to open the forum topics in their own tab. I’m referring to https://processwire.com/talk/discover/unread/ When I long press on a forum topic link in the listings it will immediately follow the link. This happens on Chrome and Safari on the iPad. Do you know of any way to stop that from happening? Thanks for any help you can provide.
  3. Perhaps this: $page->title = $nome; Should be: $page->title = $name;
  4. I believe a lot of the "trash" issues were already fixed. Can you try upgrading your site to a newer dev version? Using this module makes upgrading easy https://modules.processwire.com/modules/process-wire-upgrade/
  5. In the main navigation, can you do a modules > Refresh from the admin and then test again?
  6. For simple markdown/plain text notes with tagging, I use https://simplenote.com/ made by http://automattic.com/. It also has a mobile app. For more complex notes with images and tagging, I use Evernote.
  7. @horst - I haven't tried this, but this Inputfield module might work for you? Looks like it can show a thumbnail preview image.
  8. That did indeed fix the problem.
  9. Many thanks Robin! I’ll give it a try
  10. Hi Robin, Thanks for making this module. Just wanted to let you know that I ran into an error when I tried to export a repeater field: Let me know if I can provide any other information.
  11. Interestingly, I came across this today. https://wptavern.com/jamstacks-growing-popularity-brings-increase-in-wordpress-plugins-for-deploying-to-netlify
  12. This reminds me of a similar Drupal module that I came across. https://www.drupal.org/project/tome https://tome.fyi/ - It takes your Drupal site and makes a static version of it. You can see a demo here: I imagine that someone with enough Processwire skills could create something similar?
  13. I upgraded my sites to Processwire 3.0.135 dev, but unfortunately I'm having a problem with the new .htaccess file introduced in 3.0.135. I'm unable to get my sites to redirect from the bare domain to the www domain. Example: http://mysite.com should redirect to https://www.mysite.com I have tried commenting out these sections, but it didn't work. # ----------------------------------------------------------------------------------------------- # 9. Optionally Force HTTPS (O) # ----------------------------------------------------------------------------------------------- # 9A. To redirect HTTP requests to HTTPS, uncomment the lines below: # ----------------------------------------------------------------------------------------------- RewriteCond %{HTTPS} !=on RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301] and # 13A. Redirect domain.com and *.domain.com to www.domain.com (do not combine with 13B): # ----------------------------------------------------------------------------------------------- RewriteCond %{HTTP_HOST} !^www\. [NC] RewriteCond %{SERVER_ADDR} !=127.0.0.1 RewriteCond %{SERVER_ADDR} !=::1 RewriteRule ^ %{ENV:PROTO}://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301] If I access mysite.com it gives me the following error when accessing http://mysite.com 404 page not found (no site configuration or install.php available) If I access www.mysite.com, the website functions correctly. ------------------------------------------------------------ As a work around, I ending using this bit of code from version 300 .htaccess file. RewriteCond %{HTTP_HOST} !^www\. [NC] RewriteRule ^ http://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301] That works. I can go to mysite.com and it will redirect to https://www.mysite.com Is anyone else having trouble redirecting your domain to the https://www. version with the new .htaccess file? Here is the full .htaccess that doesn't work for me I just wanted to check with everyone here before I submit a bug report on Github. Also, does anybody know the correct location to insert redirects for other domains as well? Example myothersite.com should redirect to https://www.mysite.com
  14. I think you can just increment the version number from 100 to 101?
  15. From $config->pagefileSecure https://processwire.com/api/ref/config/ - When used, files in /site/assets/files/ will be protected with the same access as the page. Routines files through a passthrough script. I haven't used this yet, but there might be a performance hit? I'm not sure how much though? From here Wanze writes:
×
×
  • Create New...