dragan

Not sure. I found $option here https://github.com/processwire/processwire/blob/master/wire/core/WireHttp.php#L629 Don't know if you can set this in your config.php file or how. It also doesn't appear to be hookable.

Yeah, it's just that... non-techy persons are scared when you even mention tech lingo like "API key". They expect that we as developers handle all this stuff and don't bother them with it. I'm off to go reading some leaflet.js and Mapbox tutorials...

I don't think it's a multi-lang issue, since images or files can't be multi-language per se. Did you check your browser JS console for any hints or try it in another browser?

I examined the code which PW uses here for this action: https://github.com/processwire/processwire/blob/master/wire/core/WireHttp.php#L703 A few lines below you'll find the cURL function: https://github.com/processwire/processwire/blob/master/wire/core/WireHttp.php#L736 curl_setopt($curl, CURLOPT_FOLLOWLOCATION, true); This means (from the PHP docs): In other words: PW actually follows redirects when trying to fetch a file. But when something is wrongly configured on the target server, eventually it's timing out and aborting the operation.

well, your web service server has problems, that's why. Also, this URL looks wrong to me: http://gobert.websites.whoman2.be//Pictures/2602849/1920/7dfad7eb252f4efaba17907bc69e35a3.jpg Why the double slash after whoman2.be ?

https://mapsplatform.googleblog.com/2018/05/introducing-google-maps-platform.html These are just excerpts from the above link (highlighting by me). This is annoying. Does that really mean, that I have to create an account for every single site I've ever built and used Google Maps, and give Google my credit card details? Forreal? Or - even worse: pester my clients and tell them to create an account for themselves and use their CC? This is terrible business logic, Google.

If I have two PW sites that sit in separate folders, I can't be logged-in in both sites. e.g. site.com/project-a/pw-admin-slug/ site.com/project-b/pw-admin-slug/ If I login to project-a, then also login to project-b, get back to the first site, I have to login again. Is the cookie / session mechanism storing my domain? If it does, and it's meant to be some sort of security enhancement, it should not check my domain, but root-URL of the PW-installation. (strangely, this doesn't happen on localhost) Is it possible to prevent that behavior? Often I have two sites open (e.g. check to see if I have the same CKEditor setup and quickly copy and paste it, or copy a user-role)

http://processwire.com/api/multi-language-support/multi-language-fields/#getting-and-setting $language = $user->language; // save the user's language $user->language = $languages->get("french"); // change user to French Also read the next chapter there... not sure if you'll need to set output formatting on or off.

I'm not sure I understand. I can see your site (frontend) fine. The admin access is OK: so you can login @ https://www.mairie-saintoffenge.fr/gestion now? "else not 404" -> I don't understand that Take a look at the first chapter in the troubleshooting guide: https://processwire.com/docs/tutorials/troubleshooting-guide/page2 If indeed you have backend-login now, try to clear modules cache. Also, take a look at other log files than just Filecompiler (PW error log, or your Apache error log files)

I didn't really read/scan your .htaccess file - I assume it's the default one that has been generated in the install process? Do you have anything special in your config.php file? "gestion" is the backend page-slug that works fine in your local dev install? The only thing I can suggest without further infos right now: delete everything inside site/assets/cache/ folder If that doesn't fix it, try to re-move / re-upload everything from dev to prod again. Perhaps some files or folders didn't make it?

We only ask clients for permission to quote them (client testimonial). Don't know if it's legally a must, but it's certainly good form. And of course, if you show sensitive data (e.g. from the backend or if you did an intranet / web app), you should ask first (perhaps blur sensitive infos like names etc.)

What you want is AdminOnSteroids - it has lots and lots of goodies

some more reading material:

wird kommt Thanks for sharing.

Actually, hold on... I just added this JS, but it doesn't work. Is there anything else that one needs to do / add? @tpr and ideas? I'm using PW 3.0.99. Tried to load it via Cloudflare, and also with a local copy (with and without AIOM). Don't know what I did, but got it to work finally...

Thanks for adding it! I have just added it today where I think the client could probably use it (instead of making images for each formula). btw here is the link / instruction for the frontend: https://docs.ckeditor.com/ckeditor4/latest/guide/dev_mathjax.html#displaying-on-target-page

Try to add PW namespace at the very top of the .module file: <?php namespace ProcessWire; Lots of older modules can be made PW3-compatible that way... worth a try anyway.

Strange. I do see a label: This thread is old, but maybe you'll find some inspiration from here?

If it's always going to be just this one exception, this if/else is OK. If in the future there will be more image varieties, maybe use something like isotope / masonry? Another method is to always create a page-id / page-parent-id body class, and then you can use the same image class, and create variations in your CSS.

You should have posted it here instead: I guess the default image description field is from core. You could simply hide it via admin CSS. Just make sure you don't hide it for simple image fields where you don't have four desc. fields, but only the default one. So choose your CSS selector wisely

Some setup like this might do the trick: Create a table or repeater / matrix repeater field. Backend users could then create a form from scratch having these fields: type of field (dropdown / radio button) name of field field label (perhaps use PWs sanitizer to create field-name from this) optional text shown beneath the label or wherever (nice to have) checkbox "required?" a textarea field that users would have to fill in for radio buttons, checkboxes or selects (each line equals an option) Maybe additional fields for setting notification messages, cc: or similar stuff. The only caveat I could foresee: multilanguage setup.

I think so. Or even use a hook.

Well, since you prepend _init.php in PW, simply put your logic there. What kind of data is it anyway? Are we talking huge datasets in GB, or something that could be stored in a JSON file anyway? Perhaps you could run a cron job that produces a file which holds your data that needs to be pre-fetched, and do your if/else logic inside _init.php. I wouldn't really mess with the PW index.php. If it's a simple situation where you want to check if a certain page already exists inside PW, or whether you need to redirect users to the old page, then you could write simple .htaccess redirect rules. (migration / transition phase between current active system and new system which is not yet live)

That's why you should use switch() instead Do you only have text and textarea fields? How would you deal with radio buttons and checkboxes? This would be no easy task, because the editors would want to define those labels and values. Also, one author would want to make one field mandatory, while another won't. These are things you couldn't accomplish with the page selector route. Furthermore, thinking about layout - I'd expect that you could somehow define width of each field ( with percentages or a grid-like system). What's the reason you don't want to enable your client to use FormBuilder?

mySQL server has gone away - well, seems like your DB has some hickups. This sounds like the server setup is not kosher. Have you done any upgrades lately? (Apache, PHP, mySQL... config)