wube

Ignore this report. It wasn’t the plugin’s fault. It turned out that I have a post type that has the same slug as one of the translated pages. Changing the post type slug solved the problem.

I’m having the same problem.

[02-Jan-2018 12:35:46 UTC] PHP Fatal error:  Uncaught MpdfException: Unable to create output file: /var/www/clients/client2/web71/web/wp-content/uploads/woocommerce-pdf-invoices/attachments/2018/2018-01-00010.pdf in /var/www/clients/client2/web71/web/wp-content/plugins/woocommerce-pdf-invoices/vendor/mpdf/mpdf/mpdf.php:9442
Stack trace:
#0 /var/www/clients/client2/web71/web/wp-content/plugins/woocommerce-pdf-invoices/includes/abstracts/abstract-document.php(204): mPDF->Output('/var/www/client...', 'F')
#1 /var/www/clients/client2/web71/web/wp-content/plugins/woocommerce-pdf-invoices/includes/abstracts/abstract-invoice.php(321): BEWPI_Abstract_Document->generate('F')
#2 /var/www/clients/client2/web71/web/wp-content/plugins/woocommerce-pdf-invoices/includes/woocommerce-pdf-invoices.php(383): BEWPI_Abstract_Invoice->generate()
#3 /var/www/clients/client2/web71/web/wp-includes/class-wp-hook.php(286): BE_WooCommerce_PDF_Invoices->admin_pdf_callback('')
#4 /var/www/clients/client2/web71/web/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Arra in /var/www/clients/client2/web71/web/wp-content/plugins/woocommerce-pdf-invoices/vendor/mpdf/mpdf/mpdf.php on line 9442

I’m not using any of the filters you mentioned.

I can exclude this file (actually I already did it :)), but UM also prints some styles in <style> tags. I cannot exclude these ones. They’re hard-code and they’re not wrapped in any hook.

PS
If you’re working to improve styles then maybe you could use some CSS methodology? For example BEM?

OK. I see. So it would be good to add a little note about it on the plugin’s description page. Because it might be confusing for some users (like me). For a first glance, it looks like a bug.

• This reply was modified 7 years, 8 months ago by wube.

Did you even test it? It works with 4.7.*

Is there any chance to implement these UX improvements? Polylang is a great plugin but I can see a lot of confusion caused because of its UI.

Hi, @chouby!

I agree, the metabox is not very helpful in terms of usability. There’s not enough horizontal space there. I’ve noticed this issue as well while preparing the sketches.

But as you can see I’ve already saved some space removing the icons. We can get some more space:
– decreasing the horizontal padding a bit (it’s a few pixels, but still…).
– moving flags icons from the side into the input/select (set the flag as an input background, or select:after pseodo-element, etc).

Here’s a quick mockup: https://dl.dropboxusercontent.com/u/3638687/polylang/polylang-metabox-new.png
You can compare it to what we have now: https://dl.dropboxusercontent.com/u/3638687/polylang/polylang-metabox.png

Now there’s at least 70px of a free space for the buttons.

PS
There’s even a demo on the select2 site showing countries and flags selection: https://select2.github.io/examples.html

It still wordks but for taxonomies only. It doesn’t work for cpt.

dzi?ki za szybk? reakcj?.

There’s no need to modify the core files. Just use filter:

Add the following code to your functions.php

function mytheme_change_loco_admin_capability()
{
    return 'edit_posts';
}
add_filter('loco_admin_capability', 'mytheme_change_loco_admin_capability');

@tizz
thx for the explanation. let’s try to increase it a bit more.

memory limit is set to 128, but the error message says:
"tried to allocate 72 bytes", it’s lower than memory limit, so imo increasing memory limit makes no sense.

Thanks, but is the example of myfunc_set_locale() function OK? It seems no to work at all. No matter what this function returns
facebook: https://connect.facebook.net/es_ES/all.js script is always loaded with “es_ES” language code.

So the question is not how to pass correct language codes, but how to use fb_locale filter to set locale.