Forum Replies Created

Viewing 15 replies - 1 through 15 (of 16 total)
  • Forgot to mention that I’m on Windows. I checked Apache error logs and found an uncaught exception with each plugin scanned… there are no slashes in the path to the plugin. Anyway, the plugin seems to work on my live server, but failing on localhost where I actually need it.

    [php7:notice] WPE PHP Compatibility: startScan: , referer: https://localhost/wp/wp-admin/admin-ajax.php?action=wpephpcompat_start_test
    [php7:notice] WPE PHP Compatibility: timeout: 60, referer: https://localhost/wp/wp-admin/admin-ajax.php?action=wpephpcompat_start_test
    [php7:notice] WPE PHP Compatibility: lock: 1, referer: https://localhost/wp/wp-admin/admin-ajax.php?action=wpephpcompat_start_test
    [php7:notice] WPE PHP Compatibility: scan status: , referer: https://localhost/wp/wp-admin/admin-ajax.php?action=wpephpcompat_start_test
    [php7:notice] WPE PHP Compatibility: Generating directory list., referer: https://localhost/wp/wp-admin/admin-ajax.php?action=wpephpcompat_start_test
    [php7:notice] WPE PHP Compatibility: 15 plugins left to process., referer: https://localhost/wp/wp-admin/admin-ajax.php?action=wpephpcompat_start_test
    [php7:notice] WPE PHP Compatibility: Processing: AAA Master, referer: https://localhost/wp/wp-admin/admin-ajax.php?action=wpephpcompat_start_test
    [php7:notice] WPE PHP Compatibility: Attempted scan count: 1, referer: https://localhost/wp/wp-admin/admin-ajax.php?action=wpephpcompat_start_test
    [php7:error]  Uncaught PHP_CodeSniffer_Exception: Source file C:xampphtdocswpwp-contentpluginsaaa-master/ does not exist in.....
    
    Forum: Reviews
    In reply to: [Years Since] Good one!
    Plugin Author johnalarcon

    (@johnalarcon)

    You’re welcome! Glad you found it useful.

    …and thanks for taking the time to add a quick review!

    Plugin Author johnalarcon

    (@johnalarcon)

    Hi @natcornadmin,

    In English, we can use 4 suffixes st, nd, rd, and th to cover all numbers, so we can easily solve this with just a few case scenarios: a case for 1 (1st), 2 (2nd), 3 (3rd), and a case for “everything else” (Nth). However, I don’t believe all languages translate numbers in this way. The questions this raises are:

    1) Would st, nd, rd, and th suffice for all languages?
    2) If so, are these suffixes used for the exact same numbers in the sequence?
    3) Are there any other suffixes to deal with?
    4) Are there any cases where prefixes are used instead?

    Something that sounds great for one site may make little or no sense on another, particularly when language is involved. Of course, the functionality you’re requesting certainly could be implemented on your own site, but I don’t believe it would be a prudent addition for the public version of the plugin. Apologies…and thanks for taking the time to evaluate the plugin and make contact.

    John

    That is the fair and right thing to do. I think it may be that you only noticed the formatting error after installing the plugin, rather than the two actually being related. I’m sure you’ll find that getting your call to Google fonts corrected will resolve the issue. Wishing you good luck.

    I’m not associated with this plugin, but I did see your request for support. This plugin had nothing to do with your font issues. Your fonts were already broken (which the “other dude” had to point out for you). So, basically, you gave this plugin a bad review because of your own mistake. Outrageous.

    Thanks for the follow-up, Sam. I took a vacation day yesterday and feeling all kindsa recharged here. I checked the feeds right after your previous reply and it did get me a bit closer to the goal. I wasn’t able to filter the result after a few tries, so I ended up using the reviews URL. This URL returns the data I need, albeit with a healthy intermix of markup, but 5-10 minutes of code can extract just the needed bits. Thanks again for the idea and follow-up.

    Example: https://wordpress.org/support/plugin/pluginception/reviews/?filter=5

    Thanks for confirming.

    Plugin Author johnalarcon

    (@johnalarcon)

    Thanks for the additional suggestion.

    My reservation with that approach is that it does not account for pluralization, so end-users would have to manually update (add or remove the “s”) to keep the language correct (ie, 1 year, 2 years). Since the goal of the plugin is to create an automatically updating experience, I’ll be unable to implement the feature in this way.

    Instead, I’ve added another parameter to the shortcode to suppress the text. Simply add text=false to your shortcode and only the number will be returned.

    I’ve pushed this change out, but found that my version numbers didn’t work properly to trigger the update notice in the dashboard. Sorry about that; the new version is corrected so update notices will work as expected. Please deactivate, delete, then re-install the plugin and you’ll be all set. There’s no need to delete any shortcodes you may have already placed – they’ll be fine through deletion/re-install.

    Let me know if you run into any trouble.

    Cheers!

    Thanks again for the suggestion!

    Forum: Plugins
    In reply to: [Years Since] Offset years
    Plugin Author johnalarcon

    (@johnalarcon)

    Ah, ok…I see what you’re after. Yes, just adding +1 to the year will achieve just what you’re looking for.

    …and wasn’t a waste of time; I greatly appreciate your inquiry and you never know who else might have this same question.

    Cheers!

    Plugin Author johnalarcon

    (@johnalarcon)

    I’m going to leave this thread open as unresolved and will update it when I push the change out. Rather than removing the text, I’ll add an extra argument to the shortcode to optionally suppress it. Thanks again for the suggestion.

    Plugin Author johnalarcon

    (@johnalarcon)

    Hi Nathan,

    Not a bad idea. I’ll get this into the next version, which should push by Wednesday. Thanks for the suggestion.

    Cheers,

    – John

    Forum: Plugins
    In reply to: [Years Since] Offset years
    Plugin Author johnalarcon

    (@johnalarcon)

    Hi Nathan,

    Wow, I only just uploaded the plugin hours ago – figured it would be a time before anyone even found it. Thanks for giving it a spin.

    Your request is interesting. To ensure I’m understanding what you’re asking, can you give me a use-case such as how it might appear in the context of a sentence…or how you would want to use it on a site?

    Cheers!

    John

    At the time of this writing there are 118 one-star reviews, vs 69 five-star reviews. In other words there is overwhelming opinion AGAINST this addition to core.

    The plugin is neither a 1-star or a 5-star piece of work – those are fluff ratings – the better indicator are the 2, 3, and 4-star reviews.

    Moving this to GitHub.

    I came across a similar behavior when deleting all post revisions manually via the database. The (new) revisions were no longer showing on the post-edit page, and the Screen Options tab didn’t have the Revisions option anymore. Just to clarify, they were still being saved to the database.

    To fix, I went to Dashboard > Updates and reinstalled the core WordPress files. Now my revisions are showing on the post-edit page and the Revisions option is back in the Screen Options menu.

    I’ve reported this as a core bug here.

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