LostKobrakai

Did you disable access management in the template settings? You need at least have it enabled for the root page in the page-tree, otherwise PW cannot determine which user roles are allowed to see/edit/... which pages.

You can certainly achieve such a site with processwire and as it's essentially just a single type of content you need to manage (videos with outsources comments / likes) it shouldn't be to hard to create. SEO can be done in ProcessWire and there's also a module for it. But you've to determine for yourself if it fits your needs. You can always fall back to implementing own seo generation functionality. The account management won't be of any issue as long as you manage users in the backend. If you need to create custom interfaces for them in the frontend (adding videos or editing their user settings) it's certainly more work to do with all the validation and security implications you need to be aware of.

See here: http://processwire.com/api/selectors/#limit

A vm workflow is really nice especially cross platform. If you take a look at vagrant I'd suggest trying out ansible as provisioner. It's a damn nice and modular system, which can be used on almost any system you've ssh or console access.

You're using limit in both selectors and pagination does set the start value automatically, if there's non present. That's why both finds do get paginated. Add start=0 to the widget selector and it works.

You can just run this code after you imported your students as usual. Paste the code in /site/templates/admin.php before the existing line in it. This file is called for each request to the admin UI and it's a simple place for one time code. Alternatively you could also use a manually created /site/ready.php file (since pw version 2.6.7), which would be called on each request to processwire. Change up the $pages->find() call in the script and visit any site in the backend. After that just comment out the script lines, so they won't get executed twice, and check if every languages are now active.

There's currently no option in the admin UI to add images to the image-field from an external url. Via the api you can just use $page->imageField->add($url);, but I doubt that's what you're asked for. About that description field, are you talking about literally two separate fields both called description? If so that would be a bug. If there are two separate fields they should be called description and tags. If you're just talking about a single multi-line field which is labeled description, than it's caused by a setting of the image field. You can change the field to show as many lines of description as you need.

Reno does currently not even work without the default theme. But I like it way more, too.

You can search for the pages with that tag. $taggedPages = $pages->find("template=myTaggedPagesTemplate, tag=$page"); You can find docs about selectors here: http://processwire.com/api/selectors/ And some in depth into in categorizing content can be found here: https://processwire.com/talk/topic/3579-tutorial-approaches-to-categorising-site-content/

That's really a bigger thing, as the whole mpdf instance is being overwritten on save, if one is using pageOrientation or something other "constructor argument".

But more elaborated than mine.

That doesn't work. The field visibility would only close the whole repeater field. Also repeaters aren't getting much attention lately as page tables are the defacto better alternative in most cases. There where lots of requests for automatically closed repeaters before page tables came along, but I'm not aware of any solutions.

https://processwire-recipes.com/recipes/activate-all-languages/

It shouldn't matter if one is using Before, Nothing or After for that Hook as the timing isn't relevant.

I think you missed $parent = $page->parent;

Save the parent not the page, which hasn't changeds: $parent->save("offercheck");

The problem is, that we germany aren't the only ones with umlauts. https://github.com/ryancramerdesign/ProcessWire/issues/41#issuecomment-2359186 The ß=ss is already part of pw since january this year

Now I understand why it was that way. I think you'd need Ryan to implement a "two" languages strategy into ProcessPageList, so it's using labels in the user's language and urls in the fields language. Currently the module just overwrites the users language.

Well, that's certainly not great and not the logic I'd expect. I think in this case really the user-language should be used for the page list instead of the field language. You can change the behavior by changing ProcessPageEditLink.module the js config in init() to the following: $this->config->js('ProcessPageEditLink', array( 'selectStartLabel' => $this->startLabel, 'langID' => ($user->language ? (int) $user->language : 0), // Change this line 'pageID' => $id, 'pageUrl' => $this->page->url, 'pageName' => $this->page->name, 'rootParentUrl' => $this->page->rootParent->url, 'slashUrls' => $this->page->template->slashUrls, 'urlType' => $this->urlType, 'extLinkRel' => $this->extLinkRel, 'extLinkTarget' => $this->extLinkTarget, 'extLinkClass' => $this->extLinkClass, ));

By default everything in processwire is displayed in the language of the user. So if you change your user to use any of the readable languages it should be used for page select fields as well.

Or this: if($page->images->eq(0)){ }

I would never deny that wordpress pages can be done quicker than processwire ones, but you only get so far as plugins take you. And as long as we are talking simple of the shelf websites and functionality. Not to mention lack of support or interoperability of plugins. I just turned down a small budget website, because it did need an calender/booking widget, which I couldn't have build from scratch for the money. That's exactly where wp shines. But I think you can create a similarly quick workflow when creating own packages of classes, using composer packages, pw modules and html/sass components. It's just another mindset, which I just currently try to enforce. Build things in a way you can reuse it later. One good example are PageAction and IftRunnerActions. They help you encapsulating common tasks that you can reuse. If you find something in wp, which would make your life easier in processwire, just take a look at the code (keep licenses in mind) and port it over. Do you have any particular plugin/functionality that you found on your research?

Kinda like that. But as I said it depends on the usecase if such a structure is better (not so much duplication, one page could have multiple users) or worse (harder to overview in the backend).

Just noticed: It seems like the tag $page->get("{parent.title}"); does get parsed in the dev version.

I just want to quickly add: If posting the url to this forum is the seo strategy and we won't hear back from you I'm going to remove the link in the entry posting.