Karinne Cyphers

Yes, i think the issue we saw was that the module wasn't namespaced... thank you for looking into that.

Thank you for this module. I'm seeing this error after install:

We're having some performance issues with a dual server setup on AWS with an ALB in front of two custom Ubuntu servers sharing a filesystem to handle the templates/assets. We are having issues with lock files not being able to be written. Are there changes we can make to ProcessWire to make the lock files more NFS safe, perhaps setting some flags to files to make it better? Are there any are lock options like DB or memcached/redis/etc instead of files that could be used? Thank you.

+1 This would be something we could really use as well!

Thank you @kongondo This works great!

Sounds great - thank you!

We have a large number of imported posts that have no featured image tagged... moving forward the content folks will start tag a featured image, but for these older posts we have been using the summarized one when we use the renderPosts function with the small option. Since we have a number of other pages where we just need to pull out select chunks of the blog post, like the summary, featured image, etc, it would be nice to be able to get the first embedded image in blog_body.

Is there a way to call the featured image function separate from the renderPosts function? We have a need to both render that separately in some footer widgets we built plus I need to get access to the feature image for some JSON output that we provide to another team for inclusion in another web app.

We've noticed that import/export functionality has stopped working on a number of our environments. When we try to export a page, we get this error: Session: Only accepts MultiplierArray value here Inevitably we get a similar error on trying to import data as well. In the past this has worked just fine. Any thoughts on how to workaround this?

Unfortunately, Using 1.5.52 created a number of issues for us. We did downgrade our servers to PHP 7.2.x and for us, using 1.5.51 generates far fewer errors. With 52 we were having an issue where the headers weren't being set and our cookies we use for different forms weren't being set.

Hi @dragan Yes, I saw your post on the other thread. I think the problem we are having with Profields Text Blocks is that a lot of the tags we use are inline, in a paragraph of other text, not on their own line. Also we'd like to use tags on non-textarea/ckeditor fields. My concern with the approach of using a hook in the ready file is that we already do quick a bit of hook processing and we're concerned about the performance is we also start doing a regex on the bulk of the site's fields. I'd love it if there was a text formatter that would work on regular text fields plus text areas/ckeditor fields and we could pick just the couple of dozen fields we need it to work with.

We've been trying to implement Profieldts TextBlocks as a method of giving content editors an easy means to use reusable text across a range of fields and inputs. We've run into issues around the way the tags need to be on their own line for the parser to grab the tag. Essentially we want the content folks to be able to put in a simple tag like show_sometext or something like ##sometext## that will replace that tag with some type of reusable text that the content folks define. We've considered possibly using Hanna Codes for this as well. Are there other methods that would work for this? The challenge is that we have a range of different types of text fields that we would like this to work on. Thanks

Thanks for the advice @dragan... however, after trying both of those suggestions the result and the error is the same :(

@Mike RockettThank you for the advice... we've tried that but we are not having any luck. Moreover, we've noticed now that all our redirects are failing and will either error out or get stuck in a loop. We are getting this error for users not logged in with Tracy: Warning: preg_replace_callback(): Compilation failed: invalid range in character class at offset 6 in /var/www/html/site/assets/cache/FileCompiler/site/modules/ProcessJumplinks/ProcessJumplinks.module.php I'm thinking this may have something to do with PHP 7.3.x. We are running both 7.3.1 and 7.3.2 on our dev and production machines. Any advice for a workaround? Thank you.

Ah thank you - we hadn't looked into the limit modifier... that is great to know!