Forum Replies Created

Viewing 13 replies - 1 through 13 (of 13 total)
  • Thread Starter Valice

    (@valicesupport)

    We updated the changed file from that pull but unfortunately the problem persists. It’s also showing the file preview after uploading with options to “save all changes” or “insert into post” whereas it seems like it used to just take you back to the post after upload was complete (version 3.8.1). And then when I’ve clicked “insert into post” it’s put the file name in the description field.

    Thread Starter Valice

    (@valicesupport)

    We see that a 5.0 was released and testing that alongside latest version of WordPress. We can confirm this is working as expected to create a new document; however editing existing document posts with new file version is not working as expected. The original file continues to load even though it says there is a revision.

    Thread Starter Valice

    (@valicesupport)

    I can confirm this field is back as expected in 4.0.6. Thank you!

    Thread Starter Valice

    (@valicesupport)

    Updated to 4.0.6 and unfortunately this is still happening when creating new documents (says no document file is attached) and not updating existing documents when trying to add new version.

    Not seeing anything in the logs this time but just 403 errors trying to view the document URLs.

    Thread Starter Valice

    (@valicesupport)

    Hi Mark –

    Thanks for the prompt response. I think that yes, it is useful in some cases to see the bounces and delivery stats within WP instead of having to login to SMTP2Go (in some cases we don’t setup users in sub accounts for instance) but yeah only if we pass the permission in the key settings.

    So sounds like we’re in alignment so looking forward to the updates!

    Thread Starter Valice

    (@valicesupport)

    Hi Mark –

    Thanks for the response and update. FYI, we did more digging and it appears that the reason the stats doesn’t work though, is… at some point you added logic to encrypt the key before storing it, but they weren’t/aren’t decrypting the key to grab the username.

    Before –

    if ($client->consume(new Service('stats/email_summary', ['username' => substr($apiKey, 0, 16)])))

    …was/is taking the encrypted key and grabbing the first 16 digits of that, which isn’t a valid username

    After –

    $decryptKey = $apiKeyHelper->decryptKey($apiKey);
    if ($client->consume(new Service('stats/email_summary', ['username' => substr($decryptKey, 0, 16)])))

    …and returns the proper email stats for the specific API key

    Thread Starter Valice

    (@valicesupport)

    Forgot to add to this that the API key won’t activate though until the stats permissions are added. It throws the “Invalid API key entered. message.” Ideally it could be activated without those as it works when they are removed just only after it’s been activated in the plugin interface.

    Thread Starter Valice

    (@valicesupport)

    We resolved this by enabling jQuery Migrate. We understand that WordPress by default enables this but we typically choose not to because it’s only required when outdated libraries are being used. We didn’t look to see which library in your plugin was the culprit but probably the qTip library that you might want to get updated.

    Valice

    (@valicesupport)

    Was this added to the free version yet? We installed the latest version and it’s still adding the new entries to the end of the sheet after choosing “Add row at top of sheet”

    Plugin Author Valice

    (@valicesupport)

    Hi @nsantana

    Our sincerest apologies for the delayed response. We have now figured out how to receive notices from this support forum.

    Thank you for trying out our plugin! The banner(s) should appear at the top of the page by default. If your website theme has a fixed or absolute positioned header, then it’s likely showing up behind the header element and so you’ll maybe need to apply a z-index to the banner-alerts container. We’d be happy to take a look as well if you want to share the URL where it’s installed. Also – here is a link with some style examples: https://www.banneralertsplugin.com/style-samples/

    Valice

    (@valicesupport)

    We can confirm that this issue is also happening on a site we manage. Versions and plugins listed below:

    `
    ### WordPress Environment ###

    WC Version: 3.7.1
    WP Version: ❌ 5.2.4 – There is a newer version of WordPress available (5.3)
    WP Multisite: –
    WP Memory Limit: 256 MB
    WP Debug Mode: –
    WP Cron: ✔
    Language: en_US
    External object cache: –

    ### Active Plugins (10) ###

    Akismet Anti-Spam: by Automattic – 4.1.3
    Elementor Pro: by Elementor.com – 2.7.3
    Elementor: by Elementor.com – 2.7.5
    Max Mega Menu: by megamenu.com – 2.7.2
    ValiceWP: by Valice – 0.8.5
    WooCommerce Square: by WooCommerce – 2.0.6 – 2.0.7 is available
    WooCommerce Webship Integrated Quoting: by Rock Solid Internet Systems – 1.6 – Not tested with the active version of WooCommerce
    WooCommerce: by Automattic – 3.7.1 – 3.8.0 is available
    Yoast SEO: by Team Yoast – 12.4
    WP Mail SMTP: by WPForms – 1.7.0

    Valice

    (@valicesupport)

    In the ajax handler, the value of the redirect URL is always what’s posted from the form. In our scenario, we don’t know where the user should be redirected to until they login and we know who they are (different roles), so we couldn’t set a specific URL in the form post.

    The filter we applied is the exact filter WordPress applies on it’s own login form and it would be great if this fix could get rolled into the next version so we don’t have to modify your plugin and stick with your core version (and your updates) and not have a modified one.

    Thanks!

    Valice

    (@valicesupport)

    Hey There –

    What we ended up doing (because we needed custom redirects by role) was adding redirect filters in the functions file. Found here: http://codex.ww.wp.xz.cn/Plugin_API/Filter_Reference/login_redirect

    Unfortunately they didn’t work when ajax is used (as in the case of this plugin).

    So in order for those to work with this plugin, we added this line to the ajax_handler function, below the existing redirect filter logic –

    $redirect_to = apply_filters( 'login_redirect', $redirect_to, null, $user );

    It just makes it so the redirect URL can be customized like it can be using the normal login page.

    It would be nice if this change was integrated as we really like this plugin.

Viewing 13 replies - 1 through 13 (of 13 total)