johnstephens

That's what I'm used to doing with the above-mentioned Textpattern plugin, but @kongondo's suggestion was good enough for the implementation I was working on yesterday. Forgive my limited understanding, but CakePHP is something like Rails for PHP, right? So taking this suggestion would mean imitating the Cake code, not installing Cake? I just want to be sure I'm not imagining something harder than it needs to be. Thanks again! This link appears to lead to an nginx 404 error.

@SiNNuT, thanks! I agree. I just like to have a fallback in case the summary field isn't filled in every time. @kongondo's code actually checks for a summary field first, and my imitation does likewise.

Good enough for me—thank you!

Hi, Suppose I have a field called "body" that uses the CNKEditor fieldtype. On the parent page, I want to list a bunch of children and show an automatic excerpt of the body, with my own custom trailing text that links to the full content. Is there an easy way to generate a short summary of the "body" field that yields valid (X)HTML? This is such a common pattern, I imagine there's a module for it, but I searched the module directory without success; the terms I used offered no results. By way of comparison, this Textpattern plugin is mostly what I have in mind: rvm_substr.

Has this changed or moved? I enabled Advanced mode and I see the beaker at the bottom of my admin panels labeled "Advanced Mode", but I can't find a "System" tab. I looked at it using both the default and Reno admin themes, and I don't see it. Sorry if I'm overlooking something obvious. It works now. What once was lost, now is found.

I'd like to read up on importing content from Textpattern into a fresh ProcessWire installation. I know there are more than a few Textpatrons here: Is there a tutorial or thread or blog post covering this? I've used Textpattern for years. I'm very familiar with it's database schema and pretty comfortable exporting and manipulating it with MySQL. ProcessWire's schema uses a totally different paradigm, and I'm not confident that I could simply dump the data and import it into ProcessWire with the same facility. I'm happy with Textpattern for most of the sites in which I use it, but there are a few that I think using ProcessWire would be a significant boon. Thanks in advance!

This is exactly what I needed to get image uploads working on my vagrant box (scotch.box). Edit: Had this problem on another vagrant box today, searched for the solution, and found this post—but I forgot where to find the php.ini file on scotch.box. So here are the baby steps, future self: Connect to the box shell: vagrant ssh Open php.ini in vim: sudo vim /etc/php5/apache2/php.ini Find the right line: /always_populate_raw_post_data<CR> Uncomment the line: 0x Save and quit: ZZ Restart Apache: sudo service apache2 restart Exit the vagrant shell: <C-d>

The above advice was very useful to me, thank you all! Given the short turn-around time in my project schedule, I installed and configured MediaWiki, and devoted the bulk of my time on documentation and training instead of development. I found a very simple off-the-shelf skin that seems to be well-maintained, and used MediaWiki's "Common.css" page to add my own customizations. Thank you so much for the help! I'm sure the site could have been a lot leaner had I used ProcessWire, but I'm also pretty sure that I'd still be working on core functionality right now instead of delivering something they can use right away, and they need it. Thanks again!

This is just a report: When I have this module installed with FormBuilder, I can't open entries created by the latter module, thus. When I disable ProcessTextareaPreview, the error disappears. Thanks for creating this beautiful plugin! No emergency here: I just wanted to alert the author. Cheers!

Hi, I'm hammering out the details of a project for a consortium of counseling organizations. They need a new site for sharing private case information and related knowledge, and they have a very small budget. My question is: Is this site a good fit for ProcessWire, or should I build this using a Wiki engine like MediaWiki or DokuWiki? Or something else? Here are some of the requirements: The site is access-protected so that only authorized accounts can see any site content at all—approximately 20 active users at a given time. Content types: The majority of content would be informational articles in formatted text, but the site will give them easy control over a dynamic, hierarchical category list under which content can be easily organized. They will also need to upload and link to documents, including PDFs and Word docs. All content, including uploaded files, would be available only to logged-in user accounts. Multiple editors: Users can update text, create new pages, add categories, and upload and link documents. All users would have editor privileges, but they anticipate fewer than 10 will actually do it. Recent updates: They want a section that lists recent substantial updates to the site. Based on the discussion, they prefer not to include minor article edits (like a phrase being changed to bold, for example), but only edits that change the content in substance—sounds like this could easily be accomplished with an internal blog. Alerts: Any member can post a comment on an article to note current questions or issues about the content. The purpose is to resolve the questions or issues and improve the article content, not to maintain a persistent discussion about article content. Full-text search Quick navigation: A concise list of links to highest-traffic content will be available on every page. This navigation menu should be easy to add, remove, sort, or edit links by the editors. I have two further requirements, for my own sake: Simplicity of user-facing interface: I don't want the publishing software to present the editors with superfluous configuration and options they might use to break the site, or require extensive documentation for. Stablility, security, and ease of maintenance: I don't want to introduce security vulnerabilities or create long-term maintenance difficulties simply by customizing the front-end page designs. It occurs to me that Wiki software has most of the above features built-in. But I have a few misgivings about using a Wiki: Wikis include a lot of built-in functionality that I imagine would make it incredibly complex to create a skin. I know that ProcessWire would allow me to write my own markup, and keep the page designs as simple as possible. I'm also afraid that I might introduce security vulnerabilities or maintainability problems if I create my own skin for a Wiki. I know that ProcessWire enables you to include back-end functionality in front-end templates, but you don't have to do that. I'm confident that I would have to do some obvious and deliberately reckless design in order to create any security problems with ProcessWire. On the other hand, I don't want to spend weeks building out functionality that a Wiki, or other easily-available software, offers with basic installation. Any guidance, warnings, advice, or further thoughts would be greatly appreciated. Cheers! John