Tyssen

Wouldn't Processwire benefit from having some sort of global file/image management module so that you could choose assets for any page from a single location, rather than being specific to a page? I'm working a site where the client has decided to use the same content image on more than one page. At the moment, it seems the only acceptable option would be to upload the same image more than once. Creating related pages just to be able to add the same image to more than one page seems overkill for this scenario. On another site, the client wants to add images to the WYSIWYG field but first they have to add them to the page using the Images field on the page. It would be good if you could add images to a file module directly from within the WYSIWYG, because that two-step disjointed process is confusing for some people. A lot of other CMS have global file managers/media libraries, so just wondering why that feature is missing from Processwire?

This site ranks in the top 5 for nearly all the search terms relevant to it. URLs ending with .htm are still valid and always will be and don't have any negative SEO impact, so at the moment, the only argument in favour of changing them is that it will make working with default CMS behaviour easier. That might save the client a few dollars in development now, but the SEO impact if rankings were to drop could cost them a lot more. To answer Pete that SEO should remain intact, in theory that's the case, but in reality, it's not. 301 redirects aren't guaranteed to retain all the SEO strength that existed before the redirects were put in place. Any changes in URL, whether 301 redirected or not, will have an impact on SEO, even if it only for a short while, so it's not really an option for this site which has such a strong position and they don't want to alter that. It's possible that I can get away with a certain manual amount of setting pages URLs in the control panel as the client isn't likely to add new pages too often. I may also be able to use the redirect module to redirect the new URLs to the old ones (rather than the other way around) so thanks for the suggestions everyone.

Not sure if this is the right place for feature requests but a couple of mine would be: the ability to add custom attributes to inputs, for instance I like to add required aria-required="true" to required inputs to take advantage of in-built browser validation, and spellcheck="true" autocorrect="on" for textareas more control over markup for radio buttons and checkboxes so that I could omit list tags and instead use fieldsets with legends for the group label automatically add a 'required' indicator to labels for inputs that are required

I'm looking at implementing a CMS on an existing site which has very good SEO ranking position so I don't want to mess with any URLs but want to know if Processwire is the right fit for it. All the site's URLs end in .htm and are one level below the home page even though there's two sections where the pages are accessed from dropdown menus so it would make sense from a structure point of view that they be set up like: Section 1 - Page 1.a - Page 1.b Section 2 - Page 2.a - Page 2.b but with URLs like section1-pageA.htm section1-pageB.htm section2-pageA.htm section2-pageB.htm Would I be able to do this with Processwire? Does it just require some creative .htaccess writing?

Thanks Arjen, but I'm not exactly sure where in this module 'success' is actually being returned.

Using the FormTemplateProcessor module, is it possible to have the user redirected to a different thank-you page after having successfully submitted the form?

Thanks. I'll check this out next time I'm working on a PW site.

PW newbie here: could you explain a bit more about how you make that happen?

I'm quite new to PW and just want to make sure I've got this straight. Are you saying that in PW, you'd have: Categories - Category 1 - Category 2 Products - Product 1 - Product 2 and that you'd use the Pages fieldtype to relate Product 1 to Category 1, 2, etc.? Also a question for Soma, with the method you're outlining do you end up with the same page but served at different URLs? Does that not cause problems with duplicate content with the search engines?

Thanks Nate.

Thanks guys, I'll take a look at both of those.

@Soma, I'll check out the dev branch, but before I do, after posting I was thinking about it a bit more, and what would be more useful would to be able to control the markup of form output which doesn't seem possible when using the Form Template Processor module, or am I missing something? @Natetronn, you're everywhere.

I've used the Form Template Processor module to create a simple contact form but I have a requirement that placeholders be added to all the inputs and textareas. I can do that for the inputs because they have a field in the admin to do that, but textareas don't. This is my first site (and first day) using Processwire so I could be missing something obvious, but does anyone have an idea about how I'd achieve this?