dragan

Nope. Did you inspect it for JS errors? This could be anything really, maybe the browser tries to fetch something that an adblocker blocks, or just plain network or general JS problems (often caused by 3rd-party widgets).

Most fancy out-of-the-box austosuggest widgets have accessibility problems, Typeahead is one of them. It's a known issue, and there seems to be a fork with optimizations. The UK government has built their own version.

you can temporarily put it inside your _init.php file, or your template (or I guess even in site/config.php). Perhaps you can set it in .htaccess too (depends on the server setup).

Well... did you actually read it? There are useful hints in there, starting at "IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly." And there are several suggestions under "Things you can try". Take a look here:

That's "where I come from" as well :-) That has been bothering me for quite some time too - in the context of PW Pro modules that were going to be used in a ML setup. I had to translate every single string of Lister Pro, Pro Fields.... modules etc. myself, so that the client's backend-admins / authors had the interface available in their own language as well. This - to me - is a massive oversight by Ryan. You buy a Pro module, and probably every other aspect in the work-flow is ML-capable, but the actual backend GUI is not.

Not as far as I know. (only with site-profiles, but that's a completely different scenario) I guess one reason is that you probably don't want to install another language, just because a module author has a pre-defined set of languages that don't match with your own site setup. Though I assume if you would create new templates with your module, and use the __() syntax, PW will automatically create the necessary JSON translation files. Or at least, PW will list them in the language menu (where you can select templates that don't yet have a ML JSON file, and then you can create new json files and fill in the strings on the following step). <offtopic> multi-language handling in any system is complex. The more you have to deal with it, and dig deeper into the subject, the harder it gets. </offtopic>

It depends where and in how many places you will use the countries list. You could make it part of the module's config routine: Let the admin map each PW-language to the country-language-set (similar to what we all know when we import CSVs). If you need the country strings in more than just one part of the site, you could create a dedicated tpl, page-tree and with multilang title field populate the site's language fields.

@Knubbi I can't believe anyone is still considering 1&1 as a viable hosting option for... anything really. According to this, you should be able to do so. And according to this, you should grab your things and run for the hills. I can't recommend any hoster in Germany (I live in Switzerland, and all clients insist on a .ch hosting company), but I'm sure you'll find something more professional, serious and stable than what you currently have. In the long run, the extra bucks you spend will be money well-spent. (but of course, there are black sheep everywhere in the industry, not just in the lower-price area)

but your forum topic read "ProCache Error 401". Which error is it? https://developer.mozilla.org/de/docs/Web/HTTP/Status/401 https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/410 Is the same error shown also to guest-users (non-logged in)?

I've never tried to add a custom page list action myself, but it definitely seems possible, since it's hookable. I've found a few forum threads that could get you on the right track: https://processwire.com/talk/topic/10254-custom-page-actions/ https://processwire.com/talk/topic/2203-right-hook-right-after-the-pagelistactions/ https://processwire.com/talk/topic/14235-added-custom-action-but-it-doesnt-do-nothing/

Well, that's just weird, and certainly not typical for PW at all (quite the opposite). Did you check the browser console (JS errors, network panel) for hints? Apache logs? PW logs? Is this one of the default PW installations / profiles, or did you already customize a lot? I guess it's some weirdness in the server setup, or DB causing the lag. Perhaps you need to adjust your .htaccess file? Is it slow in the frontend and in the backend?

I think PW should update the first time you access a page using the new template automatically. You can disable file-compiler on a per-template basis: (perhaps best to disable it for all templates while you are still developing) setup > templates > edit template x > tab "files" > "use compiled file?"

@KarlvonKarton Not an answer to your OP, but why don't you use PW's built-in multilang feature with single or double underscores anyway? ($this->_() or __()) https://processwire.com/docs/multi-language-support/code-i18n/#translatable-strings

The gist of that thread was: Create a standalone script and bootstrap PW. (temporarily at least) switch tables to InnoDB. -> not sure about that use $pages->uncacheAll() + gc_collect_cycles() in each loop https://processwire.com/talk/topic/14487-creating-thousands-of-pages-via-the-api/?do=findComment&comment=187826

In the frontend? Or right in the backend GUI, whenever you re-order page references?

@vwatson I think your chances that @ryan sees this question is much higher if you posted in the Pro board instead. My guess is that Ryan simply didn't implement it yet...

You could try using honeypot as well: https://processwire.com/talk/topic/12872-module-comment-filter-antispam-guard/?do=findComment&comment=186248 and the CommentFilterAntispamguard module mentioned in the same thread.

Can't you just use httpUrl instead of url?

I guess so. \ comes from your Windows install... Try to clear compiled files under modules (bottom of page).

@NorbertH Ryan has created a few pro fields that are meant to be much more efficient, like Pro Fields Table and Textareas. Maybe you should try them out. Chances are, you can significantly reduce the number of fields, and hence, the number of DB queries. Most people just buy it for Repeater Matrix I guess, but Pro Fields has some other goodies as well...

A quick search for this COMODO stuff returned this interesting result: https://help.comodo.com/topic-212-1-514-5943-.html Apparently, you can fine-tune which rules to activate or not. Perhaps it's possible to narrow down the firewall rule*, and de-activate it on PW-admin pages / URLs. Whether your hoster allows this, is of course another question... * I guess it's #950107 from https://www.netnea.com/cms/2016/01/17/most-frequent-false-positives-triggered-by-owasp-modsecurity-core-rules-2-2-x/

Well, that's strange. Seems like your hoster prohibits a query with "get" (?). When you said "logs": did you refere only to PW-logs, or also Apache logfiles? Check both. You could also add ?get={firstname}%20{lastname}%20-%20{email} to any other PW page (FE + BE) and see if the same happens.

Did you check your browser JS console as well? Keep an eye on the network tab as well (you can filter by XHR).

Did you try custom (field / value) and then "modified>=today" ? (modified=today for some reason doesn't work) (manually entering modified>2018-01-01 14:00 worked for me too)

Do you mean MarkupPagerNav? I never tried to use this inside a custom admin page, I'm not even sure it's supposed to work in the backend too. Looking at the docs (filed under "frontend")... did you do step 2? Enabling Pagination Determine what template(s) you want to use pagination with. Go to Admin > Setup > Templates > [Your Template] > URLs, and check the box for: Allow Page Numbers. Save. Most likely, your template is "admin" (?), so I'm not sure if this possible at all.