Leaderboard

One thing i'd like to bring up is the fact that because the design of your website is separate from the back end and content of your website upgrades don't break your website. This is the largest bugbear I have had with WordPress and I no longer do ANY sites with it. It's as if a WordPress site has a lifespan - after a year or 2 I dreaded upgrades to the theme (yes even with child themes) as any update could break my client's site. Even plugin updates could break the site. And a site lasting more than 3 or 4 years - I haven't had one yet. Most of the sites I ran were designed by designers (I handled the back end) always with modifications - and I don't think I have particularly picky customers. Its just WordPress sites are so generic out of the box that you have to modify the theme. These days I have a designer do me a homepage and an internal page (saving me money compared with them doing the full site) and I implement the pages with various page layouts, blogs - whatever I want. Anything WordPress could have done I can do - though it can take some PHP programming to get what I want. (but I do get EXACTLY what I want) And I never have to worry about updates. I just noticed a site I was working on from last year was ver. 2.7 and as it's going live I decided that I'd send it off with the latest version. Update to 3.0.63 took less than 5 minutes (and that included taking a backup of the database) Give Processwire a try - there is a bit of a learning curve on your first few sites but after that (and easily reusing code) you'll never look back.

Well, I tried to submit the form (with test Mastercard numbers), but looking at the browser console, it seems like there is a security issue because you are trying to post from www.domain to domain. Adjust the form post URL, and see if that helps (use relative URLs, or make sure visitors always get redirected to www.). See attached screenshot. If that doesn't fix the issue, you'd have to look into lamoon.js, or jquery.validationEngine.js (But yeah, as other ppl have mentioned, this has nothing to do with ProcessWire per se.)

I've added Robin's code to AOS (unreleased yet) with some tweaks (use placeholder search character instead ::before pseudo, on enter select first match and do not submit the form, focus on expanding the icons and position the filter next to the Show all button instead floating. I've also posted a PR to the core InputfieldIcon.

As i understood it is like a support ticket area, for questions regarding pro Modules. Which lives beside the Pro Forums. It is monitored at least by @ryan

@Dinodog probably something in the form is not valid data so the form returns an error, the problem is the form shows the same message no matter what the problem is (at least when javascript is on). Your form sends data to reeflodge.com.au/php/mail.php, probably that mail.php file is where the error occurs, you can post the code here and someone might be able to figure out what the problem is.

I've looked there before. -1 Removed? +1 [edit] Just now says it is not available for my account. Remove: +9

Thanks @Robin S, I merged your codes into my aos work copy. Seems to work fine at first look but need to test a bit more to make sure there are no side effects. Bernhard's repeater profile also seems to be OK with your fixes, though it was also OK with mines.

By "Support" section I mean this: I've never even looked in this section before, and I haven't heard of anyone using it. But based on a comment today maybe some new users do go there looking for help: Is this section used by the community and monitored by anyone? If not perhaps it should be removed. Thoughts?

I thinks it's a feature of the forum software, which belongs to the store. It's probably not possible to disable one, but not the other.

@SamC I would consider myself a beginner in JS as well. There is always more to learn. Here is another resource, which helped me a lot to understand the core concepts of JS. Disclaimer: These are only the first 3.5 Hours. The full video is only available through a paid online Service.

@Dinodog, This doesn't appear to be a ProcessWire issue. However... The error is displayed from this div element located just after the closing form element: <div id="error" class="error box"> Something went wrong, please try again later. We truly apologize for the inconvenience. </div> This indicates that the javascript validation function is failing causing this div element to become visible (rather than the success message). The validation is failing for some reason, either improper user input, or a bug in the code. The form contains this hidden element which gets submitted with the other form data: <input type="hidden" name="recipients" value="developer2@puredataconsulting.com, stay@reeflodge.com.au, designer@puredataconsulting.com" /> Do you get any emails at the stay@ address? Also, the two references to pure data suggests two things. First, pure is the company that produced your web site, and two, they also get copies of all your confirmation emails (why?). Are there any error entries in your server logs which might indicate another cause? Such as the email routine? If so, please post back with that information so we might be able to help further.

+1 another + 1

Post your question(s), including any code you're having trouble with, and someone will be glad to help. Welcome to the forum.

I just returned back in town about 30 minutes ago, after being out of town with the family most of this week. As a result, I've got no blog post for this week. I'd hoped to at least get the email newsletter out, but unfortunately didn't have the necessary internet access to do so. Thankfully back online now. I'll be sending out a double issue of the newsletter next week. Hope that everyone had a good week and has a great weekend!

ProcessWire does have an router, even though it does look vastly different to what you're talking about. It's routing requests by the page template to the corresponding template.php file. What you proposed does not correspond very well with that core routing strategy, because neither urls nor the http methods are the identifying factor here. It's the pages template and the existence in the page tree. If you're looking for a more traditional mvc routing layer, you can set an alternative template file for your templates (by hook or in the backend). Just point all of them to e.g. a router.php file and use whatever router package your like to route requests to wherever the action should be handled. And about the core routing of processwire. Always keep in mind that mvc frameworks do not have something like the page tree, which is why they need a router to work on the url of the request. ProcessWire does not need that with it's approach.

Security doesn't magically get better just because files are outside the webroot. The .htaccess file does already block all access to critical files inside the processwire installation and all those files must be accessable by the webserver/php anyways, which makes things equally vulnerable in terms of those security holes which let an attacker execute his own code. And as you said for lots of hosting services it's not even an option to put library files outside the webroot. Obfuscation of the system also doesn't really improve anything considerably. Ask all those people here tracking how many attacks on wp-login.php they get even though their sites are obviously not wordpress sites. As soon as security issues are known they'll be tested no matter of how hard you try to mask your underlying system. It's already possible to share the wire folder for multiple sites, but it's to be considered that all pages also need to be updated at once, which at least for me is rather a downside than an important feature. But still this is already doable. Regarding the assets folder. ProcessWire does have a config to protect the whole assets folder essentially piping all requests to files through php to ensure access is granted for each one. If you only need to saveguard some files and prevent the php overhead for the others you can install the 3rd party "SecureFiles" module, which let's you put files out of the webroot when using this fieldtype. In regards to your point about static site generators. ProcessWire is different to Laravel in that it does depend on a database. And not only an empty one, but there need to be things installed to run ProcessWire. That's not really useful if you want some static site. If you only want html output to be generated from db data you can already use ProCache to serve static html to users with the full power of processwire to generate that html.

I'm happy to add this to the default admin theme too.