szabesz

Met too. Works on ProcessWire 3.0.62 as well.

I cannot find the topic dealing with this issue but as far as I recall in PW 3.x it no longer works as it used to be. I just used a JS hack: //replacing the logo: var logo_o = $("#branding #logo"); logo_o.attr("href", "/"); var innerHtml_str = logo_o.html(); var updated_str = innerHtml_str.replace("/wire/modules/AdminTheme/AdminThemeReno/styles/images/", "/site/templates/admin/"); //path to dir containg my logo logo_o.html(updated_str); logo_o.show(); //initially made hidden with display: none; so we need to turn it on. This is to prevent flashing. I also use a css rule to hide the logo initially otherwise it flashes once (see last line in JS above) There are various ways to add css/js to the admin, eg some: http://modules.processwire.com/modules/admin-custom-files/ http://modules.processwire.com/modules/admin-on-steroids/ Or simply in config.php: $config->scripts->add($config->urls->templates . "admin/admin_global.js"); $config->styles->append($config->urls->templates . "admin/admin_global.css");

Probably a better link in this case: *** ignore this *** EDIT: ah, I FOUND it under the "jumbotron" Anyway, thanx for the info!

I've just noticed that they added Guetzli to the ImageOptim Mac app: https://imageoptim.com/changelog.html I tested it with small images and indeed it is slooow. However, I as far as I can see with my ow eyes, turning on Guetzli generates about the same "virtual" quality as ImageOptim does without it (when we get about the same kilobytes), except that using Guetzli takes much longer. I cannot see any improvements here. Maybe it is because of the images used, I dunno. I will keep on trying but currently I missed to experience the revolution...

Hm, PW have support for this only in Pagefile: https://processwire.com/api/ref/pagefile/ -> see: URL property I wonder why only for Pagefile.

Also, with @adrian's Tracy Debugger module, you can try this to identify possible modules causing the issues: https://processwire.com/blog/posts/introducing-tracy-debugger/#module-disabler-panel Also there is a tool which might help tracing down problematic hooks: Event Interceptor Panel

Probably the best person to ask BTW, should you manage to assemble a good list, please do not forget to post it here.

Hi @Margie We have a somewhat similar thread running, have you seen it? The first two usecases in my post are good ones I think. Also there is a category: https://processwire.com/about/sites/categories/government/ Ryan's "own" site is a good example regarding complexity, features and speed but of course it is "off topic" otherwise.

I would also like to point out what @abdus also did in his example: I try to avoid expressions like these: <?php foreach($page->related_products as $matrix_item) {} foreach ($matrix_item->related_random->children('template=product, sort=random, limit=1') as $prod) {} instead: <?php $related_products = $page->related_products; foreach(related_products as $matrix_item) {} $random_children = $matrix_item->related_random->children('template=product, sort=random, limit=1'); foreach ($random_children as $prod) {} Often easier to read but most importantly one can inject bd($random_children) /Tracy/ or error_log(print_r($random_children,true)); into the code to debug the result sets. BTW, I also use the "style" @abdus presented. PHP is A templating engine itself and that is how a native PHP template looks.

Hi, Isn't there a typo here? MySQL 5.0.11 is from about 2005.

Hi, I do not think there are solid statistics to showcase but we have good blog posts you might use to pick the info you can use to persuade clients: https://processwire.com/blog/posts/building-canongate/ https://processwire.com/blog/posts/cms-critic-powered-by-processwire-again-case-study/ https://processwire.com/blog/posts/new-2.8-version-current-projects-and-pw-usage/ https://processwire.com/blog/posts/roadmap-2017/ etc... Also, you can find good case studies here: https://processwire.com/talk/forum/9-showcase/ https://processwire.com/talk/forum/16-case-studies/ https://weekly.pw/ (site of the week) Hope this helps.

How about FormCrafter for ProcessWire?

More than a year ago, with the last major Forum update because the current version does not support it anymore

+1 If you happen to "echo" it with JavaScript (let's say you cannot use PHP to echo it into the search input box because that one has already been rendered) then you can do something like: <?php if ($q) : ?> <script type="text/javascript"> $('#my-search-query-input').val(htmlentities.decode('<?= $q ?>')); </script> <?php endif; ?> where htmlentities.decode is found in https://github.com/bb87/htmlentities $q must be already sanitized of course as @kongondo pointed out, my JS example is about turning htmlentities back into regular characters which does not happen when injecting $q using JS.

While the issue of opening an Edit page being very slow can be caused by repeaters, the save operation being very slow cannot. That leads me to suspect that this issue will not be solved by moving fields to an ajax loaded tab, correct me if I'm mistaken. Not free but if you really get stuck, this one can help: https://processwire.com/api/modules/profiler-pro/ especially since Ryan's person-to-person support comes with it as well: https://processwire.com/api/modules/profiler-pro/#here-to-help-you

I guess there are other PageTable issues in the old repo as well but this one would be a great addition as well:

Me too

@ryan As far as I can understand PageTable will be updated next week in order to support pages export/import. While you are at it, can you please consider adding a second "Add new" button to top the PageTable? I did it with this JS hack: The actual issue is demonstrated here:

Great news, looks nice!

It is just a workaround, isn't it?

I guess it is normal. IDs "cannot be edited". They get deleted first and afterwards new record is created.

Thanks for the quick update! I didn't even had time to blink

According to the docs there should be no issue with it: "While we recommend letting the Options Fieldtype assign unique ID numbers for you, you may optionally assign your own. To do this, specify 123=title when adding a new option, where 123 is the ID number you wish to assign and title is the title text for your option." https://processwire.com/api/modules/select-options-fieldtype/#adding-new-options Also in the fieldtype_options table of database, option_id is int(10), so your numbers should work. Maybe a bug?

Maybe I did not have the exact same issue, sorry for being misleading. I could "uninstall" the module by clicking on the button in the admin, but after that I deleted the module files too and I got something very similar as explained by @houseofdeadleg. I just did not have time to investigate so I reverted to my backup.

Thanks for the quick update! However, I use PHP 5.6.31.