DaveP

58 minutes ago, psy said:

Lovely site and unbelievably fast.

Even fast from the other side of the world! (I can see AIOM and some srcset voodoo going on from view source.)

Easy. See 

Then have a field in that page for owner, which is the user's $user->id, add ?edit=true to the url (in a link from a user page or whatever)  then in the page template something like

<?php namespace ProcessWire;

// Code to display page contents to guests

if($input->get->edit && ($page->owner != $user->id)){
  echo 'You are not authorised to edit this page.';
} else {
  // Your code (edit form etc) here
}

Very rough, but you should get the gist.

If you get stuck, come back here and ask.

It is actually simpler than it looks, you just have to be brave! And use a disposable local install of PW, just in case you blow it to smithereens. (I'm joking of course, so long as you leave /wire/ alone, there isn't much damage you can do.)

It's a fantastic feeling of achievement seeing your own custom page in the PW backend.

On 11/7/2017 at 10:28 AM, arjen said:

This should be highlighted as an USP for ProcessWire.

@arjen is quite right. The extensibility of PW's backend isn't something you see mentioned in reviews etc.

It's only a hunch, but you're using $session->password. Password isn't normally a property of $session (it's a property of $user), so there's a chance that the $session object is being messed up by your setting it like that.

Try renaming that variable to something like 

echo "<br><h1>session[password] is </h1>".$dasession->password;

so that the $session isn't affected and see what happens.

$session->login() returns NULL on failure - see http://cheatsheet.processwire.com/session/properties-and-methods/session-login-name-pass/ rather than FALSE, so 

if ($task === false)

isn't the correct test.

15 hours ago, adrian said:

Maybe we need a tut for it

Joking apart, that's a great idea.

BTW @SamC, would you be open to accepting submissions?

Just clicking 'like' doesn't seem enough.

In Chrome, with dev tools open, you can long-click the refresh button for browser cache-busting super powers.

12 hours ago, dragan said:

I think in my case it was Typo3

I tried sooo many times to understand Typo3. And failed miserably every time.

There are/(were?) a couple of issues with AIOM running under PHP 7.0.x & 7.1.x, but they are easily rectified, if that is the issue here.

I *think* you could replace the field in the user template (a user is a page, right?) with a repeater or a PageTable (best bet) and use this to store references to 'reactions'. These being pages, could then contain fields for image/page id, kind of reaction (like/share whatever), and that the image poster has been notified of that reaction.

3 minutes ago, abdus said:

In short: it's not trivial. Or I'm making this complicated in my head.

Absolutely right, it's not trivial and it can very quickly become properly complicated.  @abdus has very quickly pretty much nailed my current thinking on this kind of functionality.

I'm currently working on just such a system (with the added extra of location-aware messages), but by breaking it down into manageable bits (I'm hoping) it becomes feasible. 

intercooler.js (which I may have mentioned before ) has beta support for Server Sent Events. I haven't tried SSE, but I'm a big fan of intercooler generally.

19 minutes ago, szabesz said:

This one?
https://processwire.com/talk/topic/17477-dummy-text-generators/?do=findComment&comment=153638

 

Aah, thank you @szabesz, I'm not going mad after all, just a little senile, perhaps.

Sorry to all for the confusion.

This is odd - I thought I'd replied to this thread on Monday but there's no sign of that post. (Has there been a problem?)

Anyhow, I accepted & merged @netcarver's pull request, thanks for that.

And I think going forward that making the module configurable so that a selection of text files can be chosen from might add to its usefulness.

45 minutes ago, netcarver said:

@DaveP I've now initiated a pull-request for your consideration.

...which I just merged/committed (whatever the proper term is). 

Going forward, I'm going to look at making this thing configurable, if only to allow a choice of dummy text file, mainly so I can switch to pommy ipsum when required.

@netcarver has already forked my module and when I figure out how, I will pull (some of) his changes into mine. Anyone else is welcome to fork and create pull requests.

For example, @horst's suggestions could be quite easily incorporated - it could also be made configurable so that different dummy text source files could be selectable, but that would be stretching my skills somewhat, so I would welcome others' input.

9 hours ago, AAD Web Team said:

Australian Antarctic Division

I'm already looking forward to seeing this!

2 hours ago, bernhard said:

you know my dummy data module? 

It's hard to keep track of these great modules!

4 hours ago, psy said:

It's so easy to use and saved me heaps of time copy/pasting from lipsum.com

That's exactly why I made it. Thanks.

On 10/6/2017 at 3:47 PM, abdus said:

Can you add a randomization logic?

Just committed changes to enable pretty much exactly what you asked.

Tags now work like this -

• [dc3] - Show 3 paragraphs ([dc:3], [dc3p] & [dc:3p] all do the same). (Same as original functionality.)
• [dc3-6] - Show 3 to 6 paragraphs randomly per page load ([dc:3-6], [dc3-6p] & [dc:3-6p] all do the same). (New stuff.)
• [dc3w] - Show 3 words ([dc:3w] does the same). (Same as original functionality.)
• [dc3-6w] - Show 3 to 6 words randomly per page load ([dc:3-6w] does the same). (New stuff.)

(Anyone who has already downloaded and is happy has no need to update - the only changes are in response to @abdus's request above.)

33 minutes ago, abdus said:

Can you add a randomization logic?

I think that can be done, although it's going to be stretching my limited regex skillz.  Going to be some time next week at the earliest, though.

I just made a textformatter module that allows you to insert dummy content (lorem ipsum style) in text fields via shortcodes.

Usage is simple - just type for example [dc3] into a textarea with this textformatter applied (plain textarea or CKEditor) and it will be replaced at runtime by 3 paragraphs of dummy content. It can also be used to populate text fields (for headings etc) using e.g. [dc4w]. This will produce 4 words (rather than paragraphs) at runtime.

The actual content comes from an included 'dummytext.txt' file containing 50 paragraphs of 'Lorem ipsum' from lipsum.com. The 50 paragraphs is arbitrary - it could be 10 or 100 or anything in between, and the contents of that file can be changed for your own filler text if you wish.

The slightly clever bit is that for any given page, the same content will be returned for the same tag, but the more paragraphs available in 'dummytext.txt', the less likely it is that two pages will get the same content (very roughly speaking - it's actually based on the page ID) so content selection is determinate rather than random, even though only the tags are saved to the db.

Update

Tags now work like this -

• [dc3] - Show 3 paragraphs ([dc:3], [dc3p] & [dc:3p] all do the same).
• [dc3-6] - Show 3 to 6 paragraphs randomly per page load ([dc:3-6], [dc3-6p] & [dc:3-6p] all do the same).
• [dc3w] - Show 3 words ([dc:3w] does the same).
• [dc3-6w] - Show 3 to 6 words randomly per page load ([dc:3-6w] does the same).

<End update on tags.>

If you think it might be useful, you can download it from GitHub and give it a try.

1 minute ago, abdus said:

This means you've set up the file field to give you an array of files (Pagefiles), you need to get the file using annual_report->first->url.
Using annual_report->url gives you the directory

See $files vs $file http://cheatsheet.processwire.com/

What happens if you echo $annual?

One fun way of demonstrating a real difference between PW and WP is to run the average WP site (preferably one chosen by the (prospective) client) and an equivalent PW site (probably from the showcase) through a tool like YSlow.

WP sites often have all these plugins, often including multiple different versions of jQuery etc etc. I just tried it on a WP site I know of and got this

Yep, 28 external javascript files and 23 external stylesheets. That's, what, 40-odd unnecessary requests?

Doing the same thing on a similar looking site from the showcase wasn't perfect - 6 js and 3 CSS (AIOM, anyone?), but it's actually a really obvious way of explaining even to a layperson that one way is very obviously better than the other - file conflicts, bandwidth, load time etc.

38 minutes ago, szabesz said:

this new module (LoginRegister) should be in the core

FWIW, I respectfully disagree.

For a lot of sites, it just isn't required. Maintainers can log in through the admin and a whole host of sites just don't need front end user management. It always struck me as silly that some other CMSs always have (had?) a visible login link on every page.

If it's a concern that it might be a harder sell to clients that this isn't part of PW core, then surely the fact that Ryan is the developer should confirm that this is effectively 'part of PW', just not installed by default.

As far as security goes, and misjudged editing of modules vs core files, there will always be people who go fiddling about in /wire/ when they shouldn't, so this functionality living in there won't necessarily help.