Forum Replies Created

Viewing 15 replies - 1 through 15 (of 18 total)
  • Thread Starter Jan Lucas

    (@jb_walton)

    Thanks!

    It’s still very strange.
    English and Italian I have tested and both work fine.

    Spanish and Dutch seem to be problematic though.
    Other plugins work fine in those languages.

    So why should that be the WP Translation Controller Level?

    Deleting all dutch language files (.mo, .po, .l10n.php, .json) solves the problem as it will fallback to English.

    Debugging this problem would be very helpful, but I don’t know how to do that.
    I tried Inspector (dev tools), .po editing, etc. Still no luck.

    Someone should be able to I guess.

    Thread Starter Jan Lucas

    (@jb_walton)

    Additional info:
    Looks like https://www.ads-software.com/support/users/javier-marcill/ had the same problem with with Spanish language. Problem was not solved.

    What can I do to solve this?
    My console (inspector) and php_log are:

    Console:

    ? GET https://testpage.nl/wp-json/database-cleaner/v1/db sizes/ 500 (Internal Server Error)                                            vendor.js?ver=1723054371:18 
    ? GET https://testpage.nl/wp-json/database-cleaner/v1/list_post types/ 500 (Internal Server Error) vendor.js?ver=1723054371:18
    ? GET https://testpage.nl/wp-json/database-cleaner/v1/list_post types/ 500 (Internal Server Error) vendor.js?ver=1723054371:18
    ? GET https://testpage.nl/wp_json/database-cleaner/v1/db sizes/ 500 (Internal Server Error) vendor.js?ver=1723054371:18
    ? [nekoFetch]
    SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
    at JSON.parse (<anonymous>)
    at vendor.js?ver=1723054371:18:63235
    at f (vendor.js?ver=1723054371:18:54494)
    at Generator.<anonymous> (vendor.js?ver=1723054371:18:55840)
    at Generator.next (vendor.js?ver=1723054371:18:54923)
    at g (vendor.js?ver=1723054371:18:60409)
    at i (vendor.js?ver=1723054371:18:60612)
    ? [nekoFetch]
    SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON at JSON.parse (<anonymous>)
    at vendor.js?ver=1723054371:18:63235
    at f (vendor.js?ver=1723054371:18:54494)
    at Generator.<anonymous> (vendor.js?ver=1723054371:18:55840)
    at Generator.next (vendor.js?ver=1723054371:18:54923)
    at g (vendor.js?ver=1723054371:18:60409)
    at i (vendor.js?ver=1723054371:18:60612)

    My php_log:

    PHP Fatal error:  Uncaught TypeError: WP_Translation_Controller::translate(): Argument #1 ($text) must be of type string, array given, called in /home/testpage/public_html/wp-includes/l10n/class-wp-translations.php on line 144 and defined in /home/testpage/public_html/wp-includes/l10n/class-wp-translation-controller.php:263
    Stack trace:
    #0 /home/testpage/public_html/wp-includes/l10n/class-wp-translations.php(144): WP_Translation_Controller->translate()
    #1 /home/testpage/public_html/wp-includes/l10n.php(195): WP_Translations->translate()
    #2 /home/testpage/public_html/wp-includes/l10n.php(306): translate()
    #3 /home/testpage/public_html/wp-content/plugins/database-cleaner/classes/rest.php(1119): __()
    #4 /home/testpage/public_html/wp-content/plugins/database-cleaner/classes/rest.php(278): Meow_DBCLNR_Rest->add_table_info_data()
    #5 /home/testpage/public_html/wp-includes/rest-api/class-wp-rest-server.php(1230): Meow_DBCLNR_Rest->rest_db_sizes()
    #6 /home/testpage/public_html/wp-includes/rest-api/class-wp-rest-server.php(1063): WP_REST_Server->respond_to_request()
    #7 /home/testpage/public_html/wp-includes/rest-api/class-wp-rest-server.php(439): WP_REST_Server->dispatch()
    #8 /home/testpage/public_html/wp-includes/rest-api.php(420): WP_REST_Server->serve_request()
    #9 /home/testpage/public_html/wp-includes/class-wp-hook.php(324): rest_api_loaded()
    #10 /home/testpage/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #11 /home/testpage/public_html/wp-includes/plugin.php(565): WP_Hook->do_action()
    #12 /home/testpage/public_html/wp-includes/class-wp.php(418): do_action_ref_array()
    #13 /home/testpage/public_html/wp-includes/class-wp.php(813): WP->parse_request()
    #14 /home/testpage/public_html/wp-includes/functions.php(1336): WP->main()
    #15 /home/testpage/public_html/wp-blog-header.php(16): wp()
    #16 /home/testpage/public_html/index.php(17): require('...')
    #17 {main}
    thrown in /home/testpage/public_html/wp-includes/l10n/class-wp-translation-controller.php on line 263
    Thread Starter Jan Lucas

    (@jb_walton)

    Hi Michael.

    Thank you very much for your quick reply.
    It works and pagespeed.web.dev isn’t complaining anymore!!
    I really appreciate you service.

    Regards,
    Jan

    Thread Starter Jan Lucas

    (@jb_walton)

    Thanks, looking forward to it.

    Thread Starter Jan Lucas

    (@jb_walton)

    After some playing around with disabling and enabling plugins I seem to have found the problem.
    The page with the problem contained a standard Gutenberg CF-7 block without a selected contact form. Editing (in wp-admin) that page and the frontend of that page gives me that 503 error.

    Re-including the CF7-block and selecting a form resolved the problem.

    Strange behaviour and seems to be e default CF7-block problem.

    Thread Starter Jan Lucas

    (@jb_walton)

    Hi Munir,

    After disabling all plugins, but Contact Form 7 and CF7 blocks, it still gives the same problem.
    After disabling Contact Form 7 plugin, the website works again.
    Very strange.

    Thread Starter Jan Lucas

    (@jb_walton)

    Hi,

    I updated the plugin and now it seems to work.
    I will start to fully test it.

    Thread Starter Jan Lucas

    (@jb_walton)

    Thanks,

    The developer of GeneratePress suggested that perhaps the plugin may not be designed for a classic PGP theme, it may rely on a block based theme that includes a theme.json.

    Does that make sense?

    Hi,

    I looked at the file and translated the strings via “Loco Translate” plugin.
    All strings can be translated, but the translated strings of ed-defined.php do not seem to be used.

    Changing the string directly in the file do work, but that is problematic with upgrades. How should I doe this?

    Or, perhaps I do something wrong?

    Thread Starter Jan Lucas

    (@jb_walton)

    Hi Tijmen,

    Finally I got this to work.
    Through a tip of the net I found:

    If you have a lot of …. elements – do not attach listener to each of them – use .on() method.

    Wanted this to share ??

    jan

    Thread Starter Jan Lucas

    (@jb_walton)

    Hi Tijmen,

    Works perfect.
    Thanks.

    Jan

    Thread Starter Jan Lucas

    (@jb_walton)

    Thanks Tijmen,

    You put me in the right direction.
    The wpsl_more_info_template is where I can change the results below the address.

    In there I see ‘description’, what gives me “the_content”.
    Instead of the content I would like to see “the_excerpt”.
    Is that possible through a filter or in any other way?

    Thanks,
    Jan

    Thread Starter Jan Lucas

    (@jb_walton)

    Hi Tijmen,

    I managed to get it to work.
    However, I had to change the registration of the wpsl_stores CPT.

    In wp-content/plugins/wp-store-locator/inc/class-post-types.php (regel 21)
    add_action( ‘manage_wpsl_stores_posts_custom_column’, array( $this, ‘custom_columns’ ), 9, 2 ); (was ….1, 2…)

    After that I could not use wpsl_stores as CPT, so I installed CPT-UI plugin to register a new CPT, using slug ‘wpsl_stores’.

    Now I can use VC for the editing Stores !!!

    Not a nice solution, but a working workaround.

    Regards,
    Jan

    Thread Starter Jan Lucas

    (@jb_walton)

    Hi,

    I just installed a fresh WP installation.
    After that I installed and activated your Store Locator.
    After that I installed Visual Composer and it’s the same problem.
    Store Locator does not show up in de Settings of Visual Composer.
    Not as post type under ‘General Settings / Default templates’ and not under Role Settings as CPT.

    So I see the Stores as CPT under Visual Composer.

    Is the Store CPT registered with special priority?

    Thread Starter Jan Lucas

    (@jb_walton)

    Hi,

    Thanks, I was referring to te page ‘Visual Composer’ / ‘Role Manager’ where Visual Composer can be activated per role.
    But on the page you are referring, the Store Locater CPT does not show up either.
    I changed the theme to a default WP theme and it doesn’t show up either.

    I will try it with a clean WP installation with only VC and Store Locater installed. Than I will install all my plugins and theme one by one to see what happens.

    Jan

Viewing 15 replies - 1 through 15 (of 18 total)