Leaderboard

This is one of the most common solutions, but as in everything with PW, it's your call how you do it! What you could do with your approach is place that php script outside of the sites directory which is protected by apache from being accessed directly for security reasons. So on your ajax request, the url is just /archive-list-render.php?q=etc Now, on you archive-list-render.php, load the PW API: <?php //This is the index.php in the web root directory, sibling to site, wire, etc. include("./index.php"); $q = $sanitizer->text($input->get('q')) $foundPages = $pages->find("somfield=$q"); //imaginary doSomethingWithPages method.. $response = doSomethingWithPages($foundPages); echo $response; Another approach for simple cases is using the same page where the ajax requests originates from, and detect if it's an ajax call otherwise render the site. This can get tricky depending on appending or prepending files into the template. (Very well exemplified on Ryan's post bellow) <?php if($config->ajax){ //ajax processing/render stuff } else{ //normal render stuff } Ryan's post:

AJAX request detection is based on the X-Requested-With header. You need to set its value to XMLHttpRequest: // via default settings: axios.defaults.headers.common['X-Requested-With'] = 'XMLHttpRequest'; // or via config object when making the request: axios.post('/post/', { pageID: this.pageID, text_heading: this.text_heading }, { headers: { 'X-Requested-With': 'XMLHttpRequest' } }) Written in browser and untested, but that's the general idea anyway ?

Nothing integrates with PW, so you have to do the work ? Use Flarum, if you want a Discourse-like experience, but with PHP. phpBB is still kicking and they use Symfony now. A new default theme is being built. Vanilla is actively developed as well. If you want to use Node.js, there is NodeBB. If you want blazing speed, you can use AsmBB. SimpleMachines and MyBB have grown stale, development is super slow.

I know you asked for a configuration but, maybe hook here? <?php $wire->addHookAfter('ProcessPageAdd::getAllowedTemplates', function($e){ $templates = $e->return; $specialTemplate = wire('template')->get('specialOne'); $parent = $pages->get(wire('input')->get->parent_id); if($parent->template != "sub"){ unset($specialTemplate->id, $templates); $e->return = $templates; } });

Today, I am glad to announce that the module support the native image field ??

This module is improved and extended successor to Version Control For Text Fields. It handles everything it's predecessor did -- providing basic version control features for page content -- and quite a bit more. Download or clone from GitHub: https://github.com/teppokoivula/VersionControl. This module requires ProcessWire 2.4.1 or later, mostly because of the file features, which require certain Pagefile and Pageimage methods to be hookable. There's no sensible way around this limitation; for those stuck with < 2.4.1, Version Control For Text Fields will remain a viable option. What does it do? While editing pages, fields with old revisions available show up with a new icon in their header bars. By hovering that icon you get a list of available revisions and by clicking any one of those the value of that particular field is reverted to that revision. No changes are made to page until you choose a revision and save the page, which means that you can keep switching between revisions to get an idea what's really changed without inadvertently causing any content to change. The module also adds a History tab to page edit. This tab opens a view to the history of current page in the form of "revisions" -- each of which is a group of changes to page fields processed during one page save (similar to revisions in various source control applications). There are three actions you can perform on these revisions: adding comments, live previewing what the page might've looked in that revision and restoring the page to specific revision. One specific feature that has been a big thing for me personally is support for file (and image) fields, as the original version control module felt rather incomplete without it. I'm hoping to take this a lot further performance, stability and feature wise, but as it stands right now, it's already included here and should be fully functional. Watch the video preview here I prepared a little screencast outlining most of this: http://youtu.be/AkEt3W7meic. Considering that it was my first screencast ever, I'd like to think that it wasn't that bad.. but I might give it another shot at some point, this time planning a bit before hitting "record" Upgrading from Version Control For Text Fields For those already using Version Control For Text Fields, I've added something extra. If you upgrade that module to it's latest version, you should see a new checkbox in it's settings screen saying "Don't drop tables during uninstall". If you check this, uninstall the module and then remove it's files (this is required in order to install Version Control), your old data should be automagically imported to Version Control. Import has only been tested with limited amounts of demo data. Proper tests are yet to come, so please be careful with this feature! Update, 21.6.2015: as of today, this module is no longer in beta. While all the regular warnings still apply (making changes, including installing any new modules, on a production site should always be considered risky) Version Control has gone through pretty extensive testing, and should be as stable as any other module out there.

In ProcessWire 3.0.160 we’ve got some major upgrades and additions to our text-matching selectors and operators. This brings a whole new level of power to $pages->find() and similar API calls, especially when it comes to search engine type queries. This blog post also includes a demo search engine that lets you test everything out live— https://processwire.com/blog/posts/pw-3.0.160/

Perfect! Thank you. I can't believe I missed that!

There is a setting in the Input tab, where you can set the year range!

Why is no one suggesting Invision Community? Its the forum software we are on right now.

"500 Internal Server Error" may be a red herring - it seems to be PW's way of avoiding display of plain old PHP errors on the front end on a production server. Can you see the PHP error log on your hosting? Do you get the error when you log in to the back end? if you can log in, Tracy will be your friend.

@desbest The answers to your questions are on that very same post: and

Thanks @Robin S, I'm going to put on my black ninja belt and solve this puzzle.

Hi @kater I've just added support for RockFinder3: https://github.com/BernhardBaumrock/RockTabulator/commit/b41362bbc4ffa29785fdfab6462ebaaabdabef41 Usage is the same as with the oder rockfinders, though the commit also includes an example ?

Happy news, the OP referred project is live now : - https://www.bhimonlineclassroom.in

You can pull in a custom CSS (see AssetPaths), where you can add anything you want.

I've heard from a few people in the last weeks, which seemed not to happy about by decision in regards to this module and especially the suggestion of RockMigrations as an alternative. Therefore I'll leave a few more thought. The module has been in it's current state for years. The last commit from my side was from Juli 2017. Just like the module continued to work till today it'll likely do in the future. There might be things to change with new PHP versions or PW versions – but maintaining working condition should be a fairly simple job. Given that I don't have any active projects anymore using the module (to the most part even for processwire in general) I personally can't and won't deal with keeping the module maintained. My suggestion for supporting RockMigration was mostly based on the fact that it's way more actively maintained and I feel it's better to group efforts behind a single project – especially given the processwire community being on the smaller end – but if RockMigration doesn't work for someone and this module does, feel free to use it. I'd be happy for anyone to pick this up and maintain it going forward, it just won't be me. /cc @Sascha Nos @elabx

@MaierGrem, do you have percentage-based widths enabled in AdminThemeUikit?

This may help.

Hello, I do not have much experience with site profile exports, I tried it out when I first started using ProcessWire but I have not used it ever since. So I cannot help you in that regard but you might want to consider different approaches as well, see: https://processwire.com/talk/topic/17302-working-on-a-webproject-with-pw/ I hope this helps.

Not really a direct answer to your issue, but using HannaCode could be a solution. Another approach, I don't know how your custom module works, but you could achieve it by extending your module or coding a little custom TextFormatter.

For those not following the Rockfinder3 thread, the latest version of Tracy includes a new barEcho() / be() method that allows you to echo directly to the bar dumps panel without Tracy trying to dump it as variables / objects. You've always been able to do this directly in the Console panel with a normal echo, but now you can do the same to the bar dumps panel.

In case you missed it, GitHub bought npm https://blog.npmjs.org/post/612764866888007680/next-phase-montage https://github.blog/2020-03-16-npm-is-joining-github/

I highly recommend everybody to do that stuff in the backend. Creating an admin page is easy and there you can to exactly the same as you would do on the frontend: Write PHP, HTML, JS + CSS. The benefit you get is huge: You can use all the power of the PW admin framework, eg, MarkupAdminDatatable, InputfieldSelect etc.; You'll also learn a lot about ProcessWire. I'd not say what you plan is piece of cake, but it's for sure doable with PW ?

Piece of cake with ProcessWire I say ?! Registration with LoginRegister Pro, feedback/rating with comments module and probably I'd think of an admin dashboard or someway to present comments/rating in a nicer way than just going to the video page and look at the fields.

I'm on BunsenLabs https://www.bunsenlabs.org/ I like it because is very minimal, and all the PC RAM goes where is needed. Unfortunately I still need sometimes to reboot in Windows for Photoshop and publishing software; so far Gimp and Inkscape or Scribus are still behind compared to Win/Mac software.

It's Linux for me anyday anytime, there are so much work I get down easily, also the terminal, I can pipe and do crazy stuff, I just installed awesomeWM and looking to play with that, I like i3 but learning C++ to customize my UI is too big of a task to take, with awesomeWM I can pick up Lua and customize my os. Been running Linux since Ubuntu 6 I think and always loved it as my programming environment.

I had once considered vanilla forums since I tested their very embedding which seemed pretty straightforward. https://success.vanillaforums.com/kb/articles/67-embedding-your-forum

A few months back I gave Linux another chance. I was looking for something that could improve my workflow in some kind or the other and yes... I'm still on Linux. Tried a lot of distros and windows managers since then - right now I'm super happy with Manjaro and the i3 (i3-gaps) window manager. Works pretty pretty well so far.

Yeah!! Long time Linux user. From Fedora Core 1 (2003) to Fedora 30 (2019). Very happy. Gideon

Maybe people should be forking some of these kind of modules and breathing some new life into them.