gmclelland

I think I had this problem in the past and I had to do the following in my template: {% if page.editable() %} <script type="text/javascript" src="{{ config.urls.templates }}scripts/jquery-1.8.3.min.js"></script> {% else %} <script type="text/javascript" src="{{ config.urls.templates }}scripts/jquery-3.2.1.min.js"></script> {% endif %} This is written in Twig, but basically it shows how to check if the page is editable then use this version of jquery, else use a different version of jquery. You might want to check your web browser's console to see if there are any errors on the page. Hope that helps

I believe you can do this with http://modules.processwire.com/modules/page-image-manipulator/ Check the docs at

Could you replacing the line with this: $this->myvar = $this->pages->get(2)->name; // problematic for some reason I have a note in my Processwire notes that say's --Extend WireData to access API variables using $this->page instead of calling wire() function every time. It also lets us get module settings directly using $this->someSetting.

Expand "Filters" on Setup > Templates and you will see it.

If a url segment for year exist, you might have to whitelist the year? https://processwire.com/api/ref/wire-input/whitelist/

What is the url for page2?

See the last paragraph on the latest blog post. https://processwire.com/blog/posts/pw-3.0.142/ Perhaps that is the issue?

Try renaming the MarkupSEO module to .MarkupSEO so you can at least access the site again while you troubleshoot it. What version of processwire are you running?

Looks like this has been corrected in iPadOS 13.1

What version of Processwire are you using? What version of PHP are you using? Older versions of Processwire might not be compatible with the newer versions of PHP 7.X.

I doubt Tracy is the problem, but to disable Tracy you can rename it to .TracyDebugger. Just FTP into the server and rename the folder in site>modules>.TracyDebugger Hope that helps

Go to /processwire/module/edit?name=TracyDebugger edit Tracy's settings: Check this option That way only Superusers can see Tracy on the live site. Hope that helps

https://github.com/processwire/processwire-requests/issues/126

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.

Perhaps this: $page->title = $nome; Should be: $page->title = $name;

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/

In the main navigation, can you do a modules > Refresh from the admin and then test again?

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.

@horst - I haven't tried this, but this Inputfield module might work for you? Looks like it can show a thumbnail preview image.

That did indeed fix the problem.

Many thanks Robin! I’ll give it a try

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.

Interestingly, I came across this today. https://wptavern.com/jamstacks-growing-popularity-brings-increase-in-wordpress-plugins-for-deploying-to-netlify

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?

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