Leaderboard

@gizomo Here are a few other options for your consideration, in case this is not ready for sharing. In no particular order (and I haven't used any yet - so no recommendations)... https://github.com/nicoknoll/ProcessNewsletter https://github.com/pmarki/ProcessSendNewsletter https://github.com/rolandtoth/pwnl https://github.com/justb3a/processwire-newslettersubscription https://github.com/dauni/processwire-newslettermanagement Hope that helps. </redirect>

Yeah keep on wp trolling, it feels good I know. But lets get real for a change, it's 2018 and not 2010 any more when wp was total crap. Plugins and safety have been improved since then. I know people who deliver websites faster than I do and make more money with wp than I do ! All they do is go to themeforest or envato and search for a cool looking template with forms, mail, client base and the whole shebang for around 50 or 80 dollar. It takes them less then a week to set it up and then sell it somewhere between 500 and 1500 dollar. And clients like the wp admin because it only takes simple mouse clicks for them to edit a wp site with new text, pics or prices. How I found out all this ? Simply because I get called by offices, real estates, photographers, etc. because their webmaster/developer took off, disappeared or they ended up with agreement conflicts. They need somebody to take over. No backups were made for half a year, cpanel access has gone, yearly domain registry has gone, etc. All they have left is the wp-admin login. So the more I got involved the more I started to see what is going on in wp land. The reason why I stick to pw ? Because working with wp dumbs you down to a copy and paster - drag and dropper. Working with pw upgrades your skills and you learn to webcode. But really, when it comes to working hours and making money, wp is the better choice.

So let's call it a scam as we should not call it web development. Playing dirty tricks is one thing and being honest and helpful is another one. I always stick to the latter. Sure, I will never become a billionaire with my "silly" attitude but at least no hordes of angry people are chasing me my whole life. Instead, I have a bunch of friends who know they can trust me.

I usually post to the blog on Fridays, but I've been working on ProcessWire-based client projects this week, so nothing new to post today. I'm back to working on the core next week and continuing the 2FA development, so will have more next week. Thanks and I hope that you have a great weekend.

We are going in circles, pw being much better than wp was not the point, we all know that.

Hello, Here come a few pointers: payment integration: http://omnipay.thephpleague.com https://www.payrexx.com/en/pricing/pricing/ https://processwire.com/talk/topic/14808-now-my-client-wants-to-add-ecommerce/ https://processwire.com/talk/topic/14511-e-commerce-tutorial-with-processwire-snipcart-your-thoughts/ member restriction: for backend: https://processwire.com/talk/topic/11499-admin-restrict-branch/ https://modules.processwire.com/modules/textformatter-soundmanager/ Subscription management https://processwire.com/talk/topic/16363-recurme-–-processwire-recurring-dates-field-custom-calendar-module/ AJAX front end editing for building playlists & "likes" while PW has frontend editing support: https://processwire.com/blog/posts/front-end-editing-now-in-processwire-3.0-alpha-4/ you might find that rolling out your on frontend solution is more versatile in your case so maybe you want to take a look at this one http://intercoolerjs.org/ or you might want to do it all in the admin: https://processwire.com/blog/posts/building-custom-admin-pages-with-process-modules/ or both frontend AND admin ? related: https://processwire.com/talk/topic/7913-podcast-profile/ https://processwire.com/talk/topic/12752-pw-podcast-theme-for-podcasts/ Hope this helps.

Try hooking after Pages::added, but you'll need to add a line to save $page within your hook when hooking that method. There's an open issue about that problem: https://github.com/processwire/processwire-issues/issues/648

http://www.flamingruby.com/blog/mapping-processwire-page-render-process/

Clean code, less code than content (ratio), and fast content delivery aren't a guarantee of good SERP results. You can build the smallest, cleanest and bestest website ever and get outranked by a crappy WordPress instance. Sometimes other things matter more than that. Links, links, links, spammy content, PBN links, more PBN links, more spammy content... all those grey to black techniques still work for almost every site. Old domain with trust but spammy content and WordPress footprint? Perfect! We already love it. New domain with better content, better UI, better load times? Are you kidding me? We will never rank that! You build clean, fast sites as a base for more. Good SERP results are a thing you have accomplish with several other things. Spend a few hundred dollars for a good, old, trustworthy domain, create 100 pages of optimized content pages for another 200 - 300 dollars, get lots of links from trusted sources (Reddit, LinkedIn, Blogs, ...), buy 10-30 more good old domains, build spammy sites with matching content, create backlinks, outreach to other spammers bloggers, get more links and you are in the Top 10 to Top 3. Don't play fair on money keywords. That won't work.

Yes @pwired have heard all the arguments. The thing that annoys me most of all is Google. Google sprouts the importance of clean code, speed, well formed HTML, blah blah blah. My PW sites deliver and yet WP sites that fail with unrecoverable HTML errors, are barely responsive, have yawningly slow load times still rate in SERP pages. How does that work?

Similar discussion:

The truth is, a simple WordPress theme modified and used in the correct way is good enough for most companies. Are they being ripped off? Probably. Will they be able to do it themselves? Unlikely. It still takes a designers eye to get the absolute best out of a theme. I worked for a company like that. 9-5, using a WordPress theme and just slightly modifying it or sometimes not at all. There's not absolute creative freedom but not everyone needs an artisan website. I enjoyed working there, the work was easy. But I wasn't crafting my skills. I now work at an established creative agency where people pay a lot of money for the designs and our designers are genius, as an aspiring designer, I'm envious. But it would never be an option for us to just use a theme. It would be dishonest to our clients that go to us for our design prowess. We find our clients find ProcessWire easier than WordPress to edit. I understand with ACF there isn't much difference between the two. But actually it's less about the forms and more about what is unique to ProcessWire - everything is a "page". The thing that threw me the most when I first moved from WordPress to ProcessWire became the absolute greatest thing about the CMS. It gives everything a level of consistency and doesn't lock you down to "taxonomy", "tags", "post types", "terms". You aren't locked down to a relationship structure and you can make a relationship structure that works for you, your clients and the website.

Noone wants to blame small offices and business that are in need for a website that won't break the bank. I blame those professional scammers that sell 80-dollar-theme-based sites as custom-made [whatever buzzword fits here] website and either charge way too much or dump prices with it.

Why? It is a very nice Plug&Pray platform. Oh well, yes, that is a skeleton in the cupboard. It is such a bad example of "simplifying" queries that even plugin developers are rolling out their replacements, eg: https://toolset.com/documentation/customizing-sites-using-php/post-relationships-api/ or WooCommerce which nowadays is the same as Automattic: https://woocommerce.wordpress.com/2018/07/17/woocommerce-custom-product-tables-beta/ "This builds on the investment we made in 3.0 which introduced Data Stores and CRUD functionality that provides a uniform way of accessing a store’s data regardless of where it is saved." and even the core WordPress team: http://v2.wp-api.org/ Hordes of talented developers are trying the get rid of the underlying crap but all in different directions. It will be interesting to see how it will turn out... In the meantime, the main effort is to replace the back-end: https://wordpress.org/gutenberg/ However, I have not read anything about getting rid of all the other junk WordPress has in big quantities. BTW, WordPress is the winner in another area: http://blog.insight.sensiolabs.com/2014/11/04/technical-debt-relevant-projects.html

Check that you have AdminThemeDefault set as the default admin theme in /site/config.php $config->defaultAdminTheme = 'AdminThemeDefault';

You are hooking Module::saveConfig instead of Modules::saveConfig.

I guess you simply need more horsepower / CPU / RAM, according to the error message... Do you have some sort of control panel @ your hosting company? You can export the database manually with phpMyAdmin or some other tool (or with CLI). And you can make a ZIP archive of the files yourself. If you can't add some ini_set() rules to temporary add more memory, I can post a few scripts for manually triggered backups (or cron-based).

Actually over five years old, but may contain some useful snippets:

Worked fine on the other site at localhost so I removed the included Tracy script, thanks!

Nobody but maintainers can reopen closed issue, but people can still comment on closed issues, initial opener or not. I cannot confirm that specifically for the processwire repos as I'm a maintainer there, but that's the behaviour I see on other repos on github.

Oh yeah... I love those super creative full stack and full service brand entrepreneur happy guys agencies that sell websites this way and claiming they are the best in the market doing highly coughstomized websites and brand building. I know agencies that charge five-figure numbers for 80-dollar-theme-based sites. Only if you do basic website jobs without any real custom data. Pages and posts slightly customized with visual page builders but that's it. A win-win situation for both sites.

It's actually not as practical an idea as I first thought because PageRenameOptions mostly works via Javascript, as @adrian explained in the support thread. But for the purposes of your module you probably don't need all the config options that PageRenameOptions provides. The "initial differences protected" option would be the main one and I think it will be possible to achieve that in PHP with the API. I'll give it a try and post something later. I see this the other way around - I think it would actually be better if PW moved to a PHP/API implementation for setting the page name. It's a bit of a problem IMO that there is no API method that provides identical naming to the JS naming in ProcessPageAdd. And I don't think the approach of requiring users of languages other than English to enter potentially thousands of character transliterations into the InputfieldPageName config is ideal. Although I don't work on non-English sites myself I think it would be good to have something like EasySlugger in the PW core, with the InputfieldPageName config only used for custom overrides. So the user only enters a title in the first step of Page Add and the page name is derived from the title in PHP. The user can easily change to a custom page name after that if need be, so it's not much of a sacrifice in return for a more consistent naming system that requires less configuration.

I've always found that the easiest way to store site settings is with a dedicated template/page. I'm a bit confused by your code because it looks like the module doesn't have any config fields, but generally speaking you can get your module config data after it is saved by hooking after Modules::saveConfig (or Modules::saveModuleConfigData if you need to support older versions of PW). You hook will run after the config is saved for any module, but you can use the first argument to compare against your module classname and return early if it doesn't match.

I completely agree with everything everyone has said thus far regarding WP. If I "have" to do anything with wordpress, I use typerocket. The framework makes it a lot more enjoyable to work with (IMHO) and has repeaters as well.

Here's some emotional support for you: WP_Query Don't get me started... If you want to get anything done which is not just a blog, you have to install ACF Pro (for custom fields). The actual query syntax/options you have at your disposal, is a nightmare. Same goes for the documentation. There's nothing "pro" in it, or about it. I was once forced to do a site with WP, where it would have been simple to display/write relationship-based pages/queries in WP, and it turned out a mess. Did it work in the end? - yes. Did I get gastric ulcer? Probably.

It's WordPress... there must be a plugin for that!

Hi @BFD Calendar I know it’s been a long time since you have reported your issue-almost one year. But I experienced the same issue on the same provider (OVH) and I found a solution. Maybe it can help: in my client interface my global PHP configuration was still set to "Legacy", I changed it to « stable » and I am now able to use the Processwire upgrade module. It can also be done in the .ovhconfig file by changing "container.image=legacy" to "container.image=stable".

The following hook should do what you want. It's based on old @Soma's post. All you have to is to edit $myslug with your random hash generator. $wire->addHookBefore("Pages::saveReady", function(HookEvent $event) { $page = $event->arguments[0]; if ($page->template->name != 'news-article') return; foreach ($this->languages as $lang) { $lname = $lang->isDefault() ? '' : $lang->id; $default = $this->languages->get("default"); $myslug = '-myslug'; if ($page->title->getLanguageValue($lang)) { $page->set("name$lname", $page->title->getLanguageValue($lang) . $myslug); } else { $page->set("name$lname", $page->title->getLanguageValue($default) . $myslug); } } });

If the module is so tightly tied to the drupal module then converting the js from jquery to pure js would mean constantly tracking changes and too much possibility to fail somewhere in the conversion. The best would be then to ask the drupal devs if they are willing to drop jquery - if yes, we could help in the first step but after that they should be able to add updates (in pure js). I don't think every drupal site is using jquery, or is it so?

I've been traveling in the second half of this week, so will release ProcessWire version 3.0.107 for next week. This week we look at the WordPress vs. ProcessWire series of videos by Jonathan Lahijani. We talk with him about the how the videos are made, what inspired them, what’s been learned, platform strengths, future plans, and more. https://processwire.com/blog/posts/wordpress-vs-processwire/

@gebeer Thanks for that simple and effective solution! Note if you are using PW3 with namespaces you must use catch(\Exception $e) instead. The redirect at the end is optional. For my forms I only redirect on success.

I posted something like this a few years ago, but that's obviously not up to date with current versions of ProcessWire. Would be interesting to create an updated version and compare these side by side, just to see how far we've come since then

I catch the login throttle messages and pass them to a session variable which is displayed on the login page: // login user try { $u = $session->login($username, $pass); } catch(Exception $e) { $session->logout(); // without this line the user will be logged in although the exception is thrown $session->login_error = $e->getMessage(); $session->redirect($pages->get('/login/')->url); } Strange thing is that without the $session->logout(), my login page will show the error message that is thrown by the login throttle but still login the user. Is this intended behaviour?