Mikel

HI guys, I am wondering if I am to focused on the problem, so that I don´t see an obvious solution, or that there is no elegant solution... ;-) Ok, here is the usecase: I am building a template with only one image-field that collects all needed images for that page. Also there are several repeater matrix fields: One for each section of the page. In each repeater matrix there is the possibility to choose one of the pages images for displaying it as "fullwidth section image" on frontend. At the moment I am doing this with a textarea, which is prone to errors, due to wrong user input. Is there another possibility to store an image reference as a textarea?

Hi, Ben, I just looked ino the WireMailChimp module: It does require the Subscribers module, doesn´t it? For my needs I altered the part whre this module is loaded and the role "subscriber" is checked. (I just run a check against my own subscriptions field) I will then allways get the same error message, no matter if subscribing or unsubscribing: 400: [EMAILADRESS] is already a list member. Use PUT to insert or update list members. Did you already got it to work properly?

Sadly I get an error when downloading the module via PW. PW Version is 2.8 Just tried with latest PW 3.0.41: Same, same... :-(

Hi, Horst, I just tried to install the module, but got 2 error messages right after downloading, regarding: AdminLinksInFrontend.module, line 153 and ProcessAdminLinksInFrontend.module, line 45 In both cases I had to remove the [...] part to get it working: self::$opcEnabled = opcache_get_status();//['opcache_enabled']; I am running PW 3.0.23 in this particular case. EDIT: Ok, now PW tells me why: I need to install PHP 5.4 or greater... Sorry for bothering you!

After upgrading the ProcessWire installation to 2.7.2 the methods next() and prev() work like they should.

No, we decided to drop everything relying on the prev() and next() methods until this gets fixed. If PW is able to return the sibling PageArray, it should to be able to traverse it, should't it?

IMHO its a bug. We decided to drop everything relying on the prev() and next() methods until this gets fixed. If PW is able to return the sibling PageArray, it should to be able to traverse it, shouldn't it?

Hi, Adrian, sorry for this! Next time I will do this in a new post. mea maxima culpa!

Hello everybody, I finally made it up: The project, still in development, is using Adrians nice module "Protected Mode". This module, if set to protected mode, seems to prevent the next() and prev() methods from working correct. problem solved. PS: After going through the "Protected Mode" module I wonder HOW this module can interfere with the next() and pre() methods... PPS: Now it gets really interesting: IT IS NOT "Protected Mode" module causing the next() & prev() methods to return NULL || nullPage object. the dependency I detected meanwhile is if the current user is logged in or not: anonymous user (aka "guest") --> everything works fine logged in user --> methods return NULL I will keep working on this one...

Hi, Soma, thats what I'm trying to find out since a couple of hours... pages are published - check pages are viewable - check page is in the pageArray because print($g->each('<p>{title}</p>')); generates the correct output of all pages - check

I get this: NullPage Object ( [template:protected] => [templatePrevious:Page:private] => [parent:protected] => [parentPrevious:Page:private] => [namePrevious:Page:private] => [statusPrevious:Page:private] => [output:Page:private] => [filesManager:Page:private] => [fieldDataQueue:protected] => Array ( ) [isNew:protected] => 1 [isLoaded:protected] => 1 [outputFormatting:protected] => [instanceID:protected] => 0 [pageNum:protected] => 1 [config:protected] => [quietMode:protected] => [createdUser:protected] => [modifiedUser:protected] => [settings:protected] => Array ( [id] => 0 ​ ​ ​ [name] => [status] => 1 [numChildren] => 0 [sort] => -1 [sortfield] => sort [modified_users_id] => 0 [created_users_id] => 0 [created] => 0 [modified] => 0 ) [data:protected] => Array ( ) [useFuel:protected] => [className:Wire:private] => [classNameOptions:Wire:private] => Array ( ) [localHooks:protected] => Array ( ) [trackChanges:Wire:private] => 0 [changes:Wire:private] => Array ( ) [_notices:protected] => Array ( [errors] => [warnings] => [messages] => ) )

Unfortunately not :-( But, as I stated before, the methods work fine in other projects, so I want to find the (to me) hidden dependency of these methods. When I output the pageArray $g everything looks fine...

Hi, Pete, I tried your code right after this: $prev = ($page->prev->id) ? '<a href="'.$page->prev->url.'">'.$page->prev->title.'</a>' : ''; $next = ($page->next->id) ? '<a href="'.$page->next->url.'">'.$page->next->title.'</a>' : ''; Unfortunately neither is working...

Yes, just added sort=title to the selector, but the method still returns NULL. The funny thing is, the same code works on all other projects so far. Thats why I am wondering about dependencies ...

While building our recent project I discovered that I could not adress the siblings of a page with the mentioned methods. Neither do the methods getNext() or getPrev() work. Are there some hidden dependencies I am not aware of? Did not find anything in the docs... To be precise: $g = $pages->find("template=glossary_detail"); $prev = "<a href='{$page->prev($g)->url}'>prev</a> "; $next = "<a href='{$page->next($g)->url}'>next</a> "; Should work, shouldn't it?

Thats what I thought first, too. But it appears that writing the proxy url (voebb-web2.voebb.local) in the $config->httpHosts array breaks the "view page" links. They link to the proxy url and we get a 404. Thats why we removed the proxy-url from the $config->httpHosts array again.

Did a full install and PW did not complain about anything, .htaccess and config look fine...

Hi, everybody! For our recent project we set up PW on our development server and everything worked as it should. Now we duplicated the project to the production environment, a server hosted by our client. Since then we get some strange error messages: When logged in as superuser: When viewing Upgrade page: When trying to load a module: (The german sentence means "Error getting data from web service URL") Anything else works, though. Our client uses a reverse proxy and claims that everything is working. But I don't think this is a PW issue, since an identical version of this project on a different server works ... Has anybody already experienced similar problems? Cheers, Mike

Hi, Nikola, we have encountered a tiny IE-problem with your nice admin-theme: http://processwire.com/talk/topic/3242-top-save-button-doesn%C2%B4t-work-in-ie9/?hl=radio-buttons#entry31869

Hi, Soma, I just figured out what caused the problem: Our client uses a custom admin-template based on the Ergo-Admin-Theme. This theme lacks the modified part in the main.js. (I added the browser check) I would consider this as a workaround, not a solution, but ok, I dont´t like debugging IE problems neither Cheers, Mike

Thanks for the Link. As I understand it, this issue is known since 2 years and there is no solution, is there?

Hello everybody, today a customer, who is using ProcessWire as a backend, encountered a strange problem: When clicking the top save button, the page reloads, but without saving the changes. The bottom save button works normally. I found the issue to be reproducible.