MatthewSchenker

Greetings, Yes, I usually don't worry about these things, but I also don't know enough about this new system. My hosting company sent me a long email with lots of things for me to confirm before upgrading, so I thought I'd better check. I'd be fine staying with CentOS, but it looks like it's not going to be supported after June 2024. Thanks, Matthew

Hey Everyone, Been a while since I posted here, although I follow lots of discussions... On WHM, on my dedicated server, I'm getting a notice that CentOS 7 will be discontinued soon, and to upgrade to AlmaLinux 8. My service provider is offering to do this over the next couple of weeks. It involves a major upgrade. I'm wondering if anyone here has conducted this, and if it all goes OK with ProcessWire? Thanks everyone! Matthew

Ryan, This looks excellent! As always, ProcessWire just does it! I've been using Pancake for several years, and it has a lot of the features you're developing. I've been happy with it. But I'd MUCH prefer to do invoicing with ProcessWire, so my invoicing would be the same framework as all my web apps. As always, thanks for your amazing work!

Greetings, I think you hit right at the point here. If people come to ProcessWire seeking a plugin-dependent, template-based system, they will have problems with it. (Of course, it's also not quite right to compare ProcessWire to Laravel, but that's at least a closer comparison). Over the past few years, I've treated ProcessWire like a Framework that includes built-in admin enhancements. My clients actually really like the default admin interface for most of their sites -- including those who came from WP. Now, comparing ProcessWire to SquareSpace (or any of the other "site builders") is ridiculous, and anyone who makes that comparison is revealing their ignorance. With all that, I'll still say what I've said for years: ProcessWire should be openly discussed as a hybrid framework/CMS. That way would reduce misunderstandings like that of this reviewer. Matthew

Greetings, That has to be one of the most ignorant "reviews" I've ever read. Thanks, Matthew

dragan, Hey, thanks for the font view! Always looking for something new for projects... Matthew

Greetings, Maybe I'm old fashioned, but the few times I tried an SSG, I ended up back with PW eventually. The first time you need to have a form of any kind, and find yourself adding PHP to your SSG... Thanks, Matthew

Greetings, Thanks wbmnfktr and OLSA for your quick responses! No JS errors, and this is a remote server. No messages in the error log. However, this is a "temporary" domain running with an address like this: ip.add.re.ss/~sitename Both times this happened, it was with installs being run that way. When I moved the installs to a sub-directory of a "real" domain, the problem went away. I'd be curious to know if anyone else is experiencing this. Thanks, Matthew

Hey Everyone... Very weird issue. Using PW 3.0.98. In a couple of my sites, after adding some pages, suddenly all pages below the "Home" page in the admin page tree become invisible. The pages still exist, since they show up on the public display, and I can see the number of pages shown to the right of "Home" in the page tree. But the pages are not accessible from the back end. Does anyone know why this would happen?

Greetings, Thanks cb2004 and Dave! When I did a quick search, among the first results that appeared was information about a WordPress malware with ".well-known." Even though I know PW is not susceptible like WP it got me worried! It is always unnerving when a folder appears in your app installation that you didn't put there! Matthew

Greetings Everyone, Just putting this out there to see if anyone else has experienced the same, and what it might mean. I noticed this morning that a folder called ".well-known" appeared in the public_html folder of one of my ProcessWire installations. Some searching seems to turn this up as potential malware. Has anyone else experienced this? And how do we prevent it? Thanks, Matthew

Greetings, Since I started this discussion, it's become natural for me to refer to ProcessWire as a framework. Like heldercervantes, I was sometimes frustrated by those who assume that WP = web development. Or when clients asked me, "How can you work without plugins?" Or when they would say, "But if we develop a custom application, then we need to depend on you" (as if using plugins means they aren't depending on anyone!). Or most frustrating of all, when they would say that "WordPress seems more secure because of how large its userbase is..." But after some years of working at this, it's become a sort of litmus test for me: I know the client is a good fit for me when they understand and want someone who develops custom applications. By the way, I can't believe this discussion was started 3.5 years ago! Thanks, Matthew

Greetings, Christophe: I see where you're at with this! For a long time, I've been emphasizing the framework aspects of ProcessWire, and I have even made direct comparisons between ProcessWire and Laravel and CodeIgniter. I use those "other" frameworks from time to time, and I am always struck with how I can really do the same things in ProcessWire, but in less time, with more fun, and feel like I am part of a better community! Along these lines, check out this adventure... -> https://github.com/hettiger/larawire Thanks, Matthew

Greetings, Good discussion... There are many ways to go. SVGs are more like DOMs within your main DOM instead of classic images. They can be used like images, but the real power comes from being able to dynamically manipulate the code behind the images. There are a couple of different paths here. Generally: - Start with something like Adobe Illustrator or Sketch to create your SVGs. - Create CSS classes to manipulate the lines of the SVG files. - Use a simple code editor to tweak the SVG elements just like you would with an HTML document. How to include the SVGs: 1. Embed the SVGs inline using <img> tags. Simply upload the SVG to your "images" directory and reference it like any other image in your ProcessWire application. 2. "Include" the SVGs in your template. You can either (A) use the same "include" function you use for other ProcessWire files, or (B) directly load the SVG code into your template. Option A is easier to maintain and allows the same SVGs to be dynamic in multiple templates, which then opens up all kinds of other possibilities! 3. Use something like Raphael to manipulate the SVG further. But this is not necessary, especially for relatively simple examples. The syntax for manipulating SVG styles is not always the same as HTML styling. Here are a couple of good references: https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Getting_started/SVG_and_CSS https://www.w3.org/TR/SVG/propidx.html https://www.w3.org/TR/SVG/styling.html As for help and resources, here are some general discussions: http://tympanus.net/codrops/2015/07/16/styling-svg-use-content-css/ https://css-tricks.com/using-svg/ https://www.smashingmagazine.com/2014/11/styling-and-animating-svgs-with-css/ Thanks, Matthew

Greetings tooth-paste, I also love SVGs and look for ways to use them anywhere I can. For years, I have been wondering why they are not more widespread, but I think there is a resurgence in their popularity now! The level of control with SVGs is amazing, and when you couple them with the flexibility of ProcessWire to manipulate the SVG elements, the possibilities are tremendous. In theory, you could have an entire site built from an SVG DOM. You probably already know about these, but I wanted to include them here: http://raphaeljs.com https://d3js.org http://snapsvg.io Each one of the above resources has its advantages. Personally, I really like Raphael. Thanks, Matthew

Greetings, File uploads are a tricky business. This is not about ProcessWire -- it's just the nature of the web. Everythng needs to be just right for the files to end up in the proper place. Here's a quick checklist of obvious reasons you could encounter for file uploads to not work, ordered roughly by likelihood: 1. Did you create the temp dirctory to store the files during processing? 2. In the ProcessWire back-end, did you set the file field to accept the right kind/number of files? 3. In your code, did you first run an initial $page->save() before doing final file-upload steps? In other words, your page should be saved (at least) two times. 4. Did you set your form to be ready for the proper enctype? 5. Did you set file-upload fields to accept multiple files (if doing this)? If none of those fit, follow up here! Thanks, Matthew

Greetings Congomonster, This will work! You need to incorporate this plugin (or one like it), into your site's existing code for handling file uploads. So you first build the form to handle file uploads, then add the plugin to target the file-upload field. Take a look at these discussions on file-uploads in ProcessWire forms: https://processwire.com/talk/topic/3105-create-pages-with-file-upload-field-via-api/ https://gist.github.com/somatonic/5236008 Thanks, Matthew

Greetings, A lot of you probably already know about this, but just wanted to post here because I think it's really neat. The New York Public Library has prepared a page with free access to 187,000+ historic images, all in high-resolution. Check it out... http://publicdomain.nypl.org/pd-visualization/ Thanks, Matthew

Greetings Everyone, Christophe: I would not worry about those "best of..." sites. Right now, the PHP community is nutty for Laravel. I like Laravel generally. However -- and I don't say this lightly -- most assessments I've seen are biased and a little rigged to help Laravel these days. For example, in that Sitepoint survey, versions 1 - 5 of Laravel are lumped into a single "popularity" number. But Yii framework (which is great, by the way), is split between version 1 and 2. We often have these discussions about increasing PW's popularity. But I wonder, maybe ProcessWire is doing well enough without pushing it? Thanks, Matthew

Greetings, Hmm... Everyone run a check. After reading this, I took a look at some logs on a few of my own projects, and what do you know -- several hits on /[domain]/wp-admin. Joss may have stumbled onto a poke-wp opportunity. Maybe we could start a movement among all non-wp CMSs to redirect such requests to a particular WordPress page. That would be mean, of course -- potentially increasing their site visits overnight by millions of hits. Thanks, Matthew

Greetings, This is great news, as I have been spending a lot of time lately looking for SSL solutions for some of my sites. I'll be putting this SSL into place in some of my smaller sites and will report back on it later. LostKobraki: nice portfolio site. Although some of the shots made me forget what we were talking about! Thanks, Matthew

Greetings, Thanks for finding this Kongondo! Of course, I could not resist posting a comment to the article! Hopefully, we'll see the "Dirt" author here on the forum soon, as I think he has a great way of communicating important aspects of ProcessWire. Or perhaps he's already here? Thanks, Matthew

Greetings, Thanks Macrura -- I fixed that! Thanks, Matthew

Greetings, Responding late to this one, but I think it's a good discussion, and may help bring more people into the ProcessWire world! I like Propel, and have often used it as my comparison for other systems. In fact, I often look at Propel and think, "How do we do this in ProcessWire?" Propel is a great ORM. A lot of Propel's CRUD functions are handled with ProcessWire in a similar fashion. Think of ProcessWire's $page and $pages elements as the equivalent of the query functions in Propel. ProcessWire essentially slims down the database calls into more readable elements. So in Propel you do this: $author = AuthorQuery::create()->findOneByFirstName('Jane'); In ProcessWire you do this: $author = $pages->find("parent=authors, FirstName=jane"); In Propel you do this: $authors = AuthorQuery::create()->find(); foreach($authors as $author) { echo $author->getFirstName(); } In ProcessWire you do this: $authors = $pages->find("parent=authors); foreach($authors as $author) { echo $author->FirstName; } There are other examples, but I think this gets the idea across. Thanks, Matthew

Greetings, No problem, as long as we end up with a process to accomplish a goal! Sorry I said to un-check all roles. Since I already had them un-checked, I did not recall that they are that way by default. I agree that it seems odd that changing "page-edit" alters the viewing access to the back-end admin page. With any system, user roles/rights are always a bit convoluted. Thanks, Matthew