Forum Replies Created

Viewing 15 replies - 1 through 15 (of 27 total)
  • Thread Starter kriskorn

    (@kriskorn)

    @dvankooten Just wanted to let you know that I went ahead and purchased a Pro license to make sure you and the team know that you have built something wonderful. The purchase process was as painless as using the plugin – just a few clicks and everything has been already activated and I am tracking outbound clicks. I also really liked how tastefully the upsell message was done.

    There are only a handful of plugins for WP that integrate with it so well with so little overhead. It feels like being part of the core. All the best for what’s to come!

    Thread Starter kriskorn

    (@kriskorn)

    @amirition This has been done. Thank you very much for taking a look!

    Thread Starter kriskorn

    (@kriskorn)

    Hi again Adrian,

    I thought at first, that the wpml-config.xml file might be the culprit as well, but it was not, I just deleted the file, re-activated the WooCommerce Product Tabs plugin and no Polylang translation functionality is still available for the Filter Sets custom post type.

    Best regards,
    Kris

    Thread Starter kriskorn

    (@kriskorn)

    Hi again Adrian,

    The plugins involved are:

    1. WooCommerce Product Tabs
    2. Polylang Pro
    3. Filter Everything

    The Polylang Pro plugin is necessary, because Filter Everything plugin checks that to activate the translation functionality.

    When Polylang and Filter Everything plugins are activated, one can go to WP Admin -> Filters -> Filter Sets and see Polylang translation columns appear for the Filter Sets custom post type. Also, the Languages “widget” shows up in the new filter set creation screen on this URL: wp-admin/post-new.php?post_type=filter-set

    When you activate the WooCommerce Product Tabs plugin, then the Polylang translation columns disappear from the Filter Sets custom post type on this URL: wp-admin/edit.php?post_type=filter-set

    Also, the Languages “widget” does not appear anymore on this URL: wp-admin/post-new.php?post_type=filter-set

    I did not find WooCommerce Product Tabs modifying any admin columns, but started tracing my way through the code deactivating certain parts of it to see what exactly might be the culprit and I got to the part, which I linked and described in the initial post above. This most likely has to be checked further to find the code responsible for deactivating Polylang translation feature for the Filter Everything plugin.

    I hope this helps clear things up.

    Best regards,
    Kris

    Thread Starter kriskorn

    (@kriskorn)

    Thank you, Adrian.

    Thread Starter kriskorn

    (@kriskorn)

    Hey, Shamim!

    Thank you very much for releasing a quick update.

    Have a great day!

    Thread Starter kriskorn

    (@kriskorn)

    @shufflehound It seems this was a false positive from one of our internal tools. Sorry about the false alarm and thank you for replying so quickly. I will mark this as resolved.

    Hey there!

    As people above, websites that have the latest version of the plugin are showing the below error message:

    Fatal error: Uncaught Error: Class 'CMTT_Pro' not found in /srv/htdocs/wp-content/plugins/enhanced-tooltipglossary/glossaryFree.php:978
    Stack trace:
    #0 /srv/htdocs/wp-content/plugins/enhanced-tooltipglossary/glossaryFree.php(21): CMTT_Free::initFiles()
    #1 /srv/htdocs/wp-content/plugins/enhanced-tooltipglossary/enhanced-tooltipglossary.php(96): CMTT_Free::init()
    #2 /wordpress/core/6.0.3/wp-settings.php(428): include_once('/srv/htdocs/wp-...')
    #3 phar:///usr/local/bin/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1317): require('/wordpress/core...')
    #4 phar:///usr/local/bin/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1235): WP_CLI\Runner->load_wordpress()
    #5 phar:///usr/local/bin/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start()
    #6 phar:///usr/local/bin/wp-cli/vendor/wp-cli/wp-cli/php/bootstrap.php(78): WP_CLI\Bootstrap\LaunchRunner->process(Object(WP_CLI\Bootstrap\BootstrapState))
    #7 phar:///usr/local/bin/wp-cli/vendor/wp-cli/wp-cli/php/wp-cli.php(27): WP_CLI\bootstrap()
    #8 phar:///usr/local/bin/wp-cli/php/boot-phar.php(11): include('phar:///usr/loc...')
    #9 /usr/local/bin/wp-cli(4): include('phar:///usr/loc...')
    #10 {main}
      thrown in /srv/htdocs/wp-content/plugins/enhanced-tooltipglossary/glossaryFree.php on line 978

    Unfortunately, it seems the versions of the plugins are not tagged, so it is not possible to easily roll back to the previous version. Once the above is fixed, may I also ask for you to tag your releases? Thank you!

    Thread Starter kriskorn

    (@kriskorn)

    Hey, Nicolas!

    Thank you very much for releasing the fix so quickly and also tagging all your releases. Much appreciated!

    Thread Starter kriskorn

    (@kriskorn)

    Thank you very much for the quick fix, Joachim.

    Thread Starter kriskorn

    (@kriskorn)

    Joachim, here is the stack trace:

    Fatal error: Uncaught Error: Class 'WPCAMeta' not found in /srv/htdocs/wp-content/plugins/restrict-user-access/level.php:260
    Stack trace:
    #0 /srv/htdocs/wp-content/plugins/restrict-user-access/level.php(246): RUA_Level_Manager->_init_metadata()
    #1 /srv/htdocs/wp-content/plugins/restrict-user-access/app.php(596): RUA_Level_Manager->metadata()
    #2 /wordpress/core/5.9.1/wp-includes/class-wp-hook.php(307): RUA_App->process_level_automators('')
    #3 /wordpress/core/5.9.1/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array)
    #4 /wordpress/core/5.9.1/wp-includes/plugin.php(474): WP_Hook->do_action(Array)
    #5 /wordpress/core/5.9.1/wp-includes/pluggable.php(48): do_action('set_current_use...')
    #6 /wordpress/core/5.9.1/wp-includes/user.php(3375): wp_set_current_user(0)
    #7 /wordpress/core/5.9.1/wp-includes/pluggable.php(70): _wp_get_current_user()
    #8 /wordpress/core/5.9.1/wp-includes/user.php(628): wp_get_current_user()
    #9 /wordpress/plugins/jetpack/10.8-a.1/jetpack_vendor/automattic/jetpack-connection/src/class-manager.php(687): get_current_user_id()
    #10 /wordpress/plugins/jetpack/10.8-a.1/jetpack_vendor/automattic/jetpack-tracking/src/class-tracking.php(240): Automattic\Jetpack\Connection\Manager->is_user_connected()
    #11 /wordpress/plugins/jetpack/10.8-a.1/class.jetpack.php(944): Automattic\Jetpack\Tracking->should_enable_tracking(Object(Automattic\Jetpack\Terms_Of_Service), Object(Automattic\Jetpack\Status))
    #12 /wordpress/core/5.9.1/wp-includes/class-wp-hook.php(307): Jetpack->configure('')
    #13 /wordpress/core/5.9.1/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array)
    #14 /wordpress/core/5.9.1/wp-includes/plugin.php(474): WP_Hook->do_action(Array)
    #15 /wordpress/core/5.9.1/wp-settings.php(450): do_action('plugins_loaded')
    #16 phar:///usr/local/bin/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1317): require('/wordpress/core...')
    #17 phar:///usr/local/bin/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1235): WP_CLI\Runner->load_wordpress()
    #18 phar:///usr/local/bin/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start()
    #19 phar:///usr/local/bin/wp-cli/vendor/wp-cli/wp-cli/php/bootstrap.php(78): WP_CLI\Bootstrap\LaunchRunner->process(Object(WP_CLI\Bootstrap\BootstrapState))
    #20 phar:///usr/local/bin/wp-cli/vendor/wp-cli/wp-cli/php/wp-cli.php(27): WP_CLI\bootstrap()
    #21 phar:///usr/local/bin/wp-cli/php/boot-phar.php(11): include('phar:///usr/loc...')
    #22 /usr/local/bin/wp-cli(4): include('phar:///usr/loc...')
    #23 {main}
      thrown in /srv/htdocs/wp-content/plugins/restrict-user-access/level.php on line 260

    Although the plugin version is 10.8-a.1 above, this happens with stable release of Jetpack 10.7 as well: https://www.ads-software.com/plugins/jetpack/

    PHP version: 7.4

    Thread Starter kriskorn

    (@kriskorn)

    Thank you very much for a quick answer, Joachim. It seems this appears in a combination with another plugin and I reported this too hastily. Sorry about that!

    I will do some more testing and report back later.

    Hey!

    Please add the below code to the Custom CSS of your theme:

    .top-footer-block .widget-title {
        color: #fff !important;
    }

    This code block will make the Footer Titles white.

    And you can make the space smaller in Navigation when you make the logo a bit smaller:

    #site-branding .site-logo {
        width: 50% !important;
    }

    Modify the 50% value to your liking.

    I hope this information is helpful to you.

    Merry Christmas!
    Kris

    Hi again,

    In this case please visit the website you have downloaded the theme and contact their customer support – https://www.themeum.com/wordpress/themes/prolog-minimal-responsive-blogging-wordpress-theme/

    I am sure that they will be able to help you out.

    All the best,
    Kris

    Forum: Fixing WordPress
    In reply to: link to images

    Hi again,

    Could you please test this solution – https://wordpress.stackexchange.com/questions/26858/wordpress-in-a-sub-directory-but-not-images as well?
    Sorry, this was removed in WordPress 3.5.

    Could you please provide me with your WordPress Admin details (Website URL, Username and Password) and FTP details (Server Address, Username and Password), so I could take a closer look at the issue? Thank you!

    PS! – Please make sure that you send them to [email protected] and not post here, as they will be public otherwise!

    If I am asking too much, then I understand, but I would definitely like to find out, what is the issue at the moment.

    All the best,
    Kris

    • This reply was modified 8 years, 2 months ago by kriskorn.
Viewing 15 replies - 1 through 15 (of 27 total)