Forum Replies Created

Viewing 15 replies - 1 through 15 (of 81 total)
  • Thread Starter phaser32

    (@phaser32)

    Hi aiswaryaxyzscripts,
    I recently received a notification in my X Developer Console stating:
    “The Free plan has been deprecated. The Free access tier no longer includes general access to API endpoints. We recommend switching to our new Pay Per Use plan…”
    This change means the free tier no longer supports posting endpoints required by your plugin. Unfortunately, as we are not willing to pay for X’s new pay-per-use or subscription API tiers, we can no longer use WP Twitter Auto Publish on our WordPress sites.
    Thank you for the great work on the plugin over the years. We wish you success with future updates and alternatives.
    Warm regards
    Ale

    Thread Starter phaser32

    (@phaser32)

    Sorry Florant, I found how to use tags. Basically the first value in the “general” options is the prefix while the field below allows the insertion of cf7 tags.
    Thanks sorry for the inconvenience

    Ale

    Thread Starter phaser32

    (@phaser32)

    @cbacigalupo These are different ways of approaching and managing released platforms (regardless of the underlying technology). You mentioned large companies like Toyota Argentina, and in that case, it doesn’t surprise me that the Client gets involved in the details. If you have a management contract, it’s normal for the Client to “not want to know anything” and to take aspects like security and maintenance for granted. The situation changes when the Client is small to medium-sized; they fundamentally lack the awareness, and if elements like security and maintenance aren’t properly conveyed, it’s clear that the “uninformed” Client doesn’t appreciate any input, failing to recognize its added value. In your case, where you sell and manage the infrastructure/hosting side, it obviously allows you to “bury” routine maintenance in the costs, but you understand that it wouldn’t be sustainable otherwise (no one works for free). This is why small Clients find themselves in two situations: automatic updates and disabled updates. In this case, two scenarios emerge: – Automatic updates > risk of ending up with the site locked down in case of plugin and/or script collisions, and NO ONE assigned to fix the problem. – Disabled updates > risk of being exposed to potential attacks and system breaches. From my personal experience, we’ve acquired many Clients who found themselves in these two situations, who subsequently not only appreciated the contribution to restoring the platform but expressly asked to be followed as a focal point for any problem related to the site (mail, backups, updates, etc.). Finally, regarding your statement where you claim to give more importance to “core error to a security breach,” some considerations need to be made. First of all, the “cost and benefit of this approach” must be evaluated, assessing together with the Client whether they are willing to run the risk of service downtime and, at the same time, assessing the risk of exposure to potential new breaches (imagine an e-commerce that doesn’t work for hours or days). There are many solutions that can be implemented (creation of test and development environments, creation of redundant clusters, backup and restore systems), but as you rightly pointed out, it all depends on how much the Client is willing to pay. Everything else we experience daily is history…
    Warm regards
    Alessandro

    Thread Starter phaser32

    (@phaser32)

    Good morning everyone,
    Sorry if I interject … I don’t want to stand up for developer but it is an obvious error. I personally made a verification with Diffmerge (taking the versions 3.3.3 and 3.3.2 from this site) and in fact the versions are different (a series of changes have been made). This means that the developer erroneously did not update the version but the 3.3.3 content is updated.
    In Italy we say “who works fails” so the aggressive criticisms I have read, are not corrrect at my advice.
    Finally I would like to answer @galbaras: what you say is quite trivial as shareable. When you manage (in a professional way) a platform made with WordPress a best practice is precisely to disable automatic updates. This is because (unfortunately on more than one occasion I have experienced it personally) some updates can collide with the core or with other plugins, manifesting the white screen or error log that must be managed. Of course, this applies to information technology not for users who install blogs and manage everything in “Plug & pray” mode.
    We await for developer feedback, reminding to everyone that for free plugins you have to have respect and gratitude for the work carried out.
    Warm Regards
    Alessandro

    Same here…

    Thread Starter phaser32

    (@phaser32)

    I apologize, but unfortunately after more in-depth analysis we noticed two problems. The first update of your plugin did not go well (some files were corrupted). The second problem was related to a cache problem on our server. We can close the report. Thank you for your attention.
    Kind regards

    Ale

    • This reply was modified 1 year, 9 months ago by phaser32.
    Thread Starter phaser32

    (@phaser32)

    Sorry but on another website we updated to version 3.0.3. but all the site is locked because of your plugin (we noticed a lot of error on server log). We had to roll back.
    Do you plan to fix these issue ?

    Thread Starter phaser32

    (@phaser32)

    Hi, the problem was a custom function that we wrote that created conflicts. By the way: deactivate ALL other plugins except Wp-Member and probably You’ll verify that is not the culprit. Then reactivate one by one other plugin and when the problem comes again … boom ! You got it ! There’s no other way. I know is annoying but that’s it (obviously if You have not a “speaking” error log).

    Warm regards

    Ale

    • This reply was modified 1 year, 9 months ago by phaser32.
    Thread Starter phaser32

    (@phaser32)

    Thank you for the feedback. we will wait confidently

    Warm regards

    Ale

    Thread Starter phaser32

    (@phaser32)

    Good morning, I solved the issue and I have to say that You plugin was not the culprit.
    Sorry for misunderstanding.

    Warm regards

    Ale

    Thread Starter phaser32

    (@phaser32)

    Good morning, I probably misunderstood the request. We do not need to carry out any traffic analysis, but rather we would need to discriminate against a user who accesses the webapp/PWA from a “normal” browser simply to show or hide some elements.
    Thx for any support
    Warm regards

    Ale

    Thread Starter phaser32

    (@phaser32)

    Good morning, first of all thanks for the reply. I gave a simple example and it doesn’t matter where the wording “YOU ARE ON PWA” appears, it could be in the footer or in the header. In reality what I’m trying to do is understand how to discriminate a user who views the site in pwa mode from another who is simply viewing it as a site from the browser.
    thx

    Thread Starter phaser32

    (@phaser32)

    Hi Florant, I ask you to forgive me very much.
    I didn’t realize that in the configuration of the sending form of your plugin there is precisely the “Select a page to display after sending the form (optional)” function.
    I therefore confirm not only the correct functioning of the plugin but also the excellent work done.
    I leave a trace of the post so that it can be of help to someone who has the same need.
    Thanks and sorry if I wasted your time.
    Warm regards
    Ale

    Thread Starter phaser32

    (@phaser32)

    Good morning Mr Takayuki,
    I identified the problem and I explain it below because maybe it could be useful to someone.
    In reality the problem is linked to a custom function that I had created to change the format of emails sent in PDF format with the “Send PDF for Contact Form 7” plugin. The changes I made were in the functions.php file of the theme used.
    The code I entered was the following:


    /* START CHANGE DATA FORMAT CF7 */ add_filter( ‘wpcf7_posted_data’, ‘custom_format_all_dates’ ); function custom_format_all_dates( $posted_data ) { foreach ( $posted_data as $key => $value ) { if ( preg_match( ‘/^\d{4}-\d{2}-\d{2}$/’, $value ) ) { $date = date_create_from_format( ‘Y-m-d’, $value ); $formatted_date = date_format( $date, ‘d/m/Y’ ); $posted_data[ $key ] = $formatted_date; } } return $posted_data; } / END CHANGE DATA FORMAT CF7 */


    Until contact form 7 version 5.8.7 everything worked correctly but after the 5.9 update it started to stop sending emails.
    Most likely because the way in which the data is wrapped before being sent has changed.
    I removed the change and everything works correctly (although the “Send PDF for Contact Form 7” plugin continues to send the date in the wrong format (but at this point it no longer concerns it).
    I apologize for not delving deeper into the topic sooner and for wasting your time.

    Have You a great day
    Ale

    • This reply was modified 2 years, 2 months ago by phaser32.
    Thread Starter phaser32

    (@phaser32)

    Hi,

    here is the list of installed plugins:

    Classic Widgets
    Contact Form 7
    Contact Form 7 - Dynamic Text Extension
    Contact Form 7 Signature Addon
    Disable Gutenberg
    Docket Cache
    EWWW Image Optimizer
    Favicon by RealFaviconGenerator
    Heartbeat Control by WP Rocket
    Jquery Validation For Contact Form 7 (Lite)
    Loginstyle Admin Login Customizer & Styler Developer Version
    plugin load filter
    Post Types Order
    Responsive Pricing Table
    Send PDF for Contact Form 7
    SVG Support
    The7 Elements
    Ultimate Addons for WPBakery Page Builder
    Under Construction
    WeePie Cookie Allow
    Wordfence Security
    WP Mail SMTP
    WP-Optimize - Clean, Compress, Cache
    WPBakery Page Builder
    WPS Hide Login
    Yoast Duplicate Post
    Yoast SEO


    But You should consider that we have noticed the same behaviour in other website with different config and plugins installed.
    Thanks for attention

    Warm regards

    Ale

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