Mikel

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?

The first one is simple. The host mentioned by the error message is the host you're accessing the installtion with, therefore this host needs to be set as one of $config->httpHosts, like it's described there. The other ones let it seem like your processwire installation has no access to the internet. 

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.

Do a full install of processwire on the hosting server, during the setup processwire informs about necessities

and errors. Just check how the setup ends and see if this leads you to an answer. Did you check the .htaccess

and config.php files already ?

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

It has been fixed. As by this thread you can see we decided to turn off the top save buttons in all IE. Since it's only a cloned button using jquery there is a $.browser.msie check in the main.js that prevent the button from cloning. I just tested in IE and the top save button doesn't show, which is correct.

Maybe you can provide more infos to find out why it's still showing in your case? I guess you use an admin theme that is older or a PW version that is older.

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.