Forum Replies Created

Viewing 15 replies - 1 through 15 (of 106 total)
  • Thread Starter dasigna

    (@dasigna)

    finally:

    CF7 eliminated, same for Image Comparison.
    -> full minifying with AO, inline js included etc., no wp-includes/js/dist or other ‘wp-includes’v exclusion –> no more errors, very nice source, ~3-400kb less to load. everythings working well.

    so no AO issue, but seems like its getting harder to optimize more and more… keep up your great work anyways ??

    meanwhile problem solved, many thanks.

    Thread Starter dasigna

    (@dasigna)

    so AO+CF7 with js/dist excluded (and “include inline JS” off) still gives errors for you?

    no. but it gives still a too big amount of requests and lots of nasty inline js in source ??

    so goodbye to CF7. no headaches then!

    Thread Starter dasigna

    (@dasigna)

    and if you -briefly- switch theme?

    honestly didnt do so. its GeneratePress theme – in none of the numerous cases with errors during the last 5+ years this was the culprit. so did not test this, except from deactivating the pro version.
    wont expect any difference if doing so ??

    ah, I see you don’t have wp-includes/js/dist in your JS exclusion list, which is excluded by default, I assume (hope) things are not broken with that exclusion active?

    nothing broken. everythings fine.
    in contrary things get worse if doing so with CF7 installed …

    • This reply was modified 3 years, 9 months ago by dasigna.
    • This reply was modified 3 years, 9 months ago by dasigna.
    Thread Starter dasigna

    (@dasigna)

    so you have the error even if only using CF7+AO?

    yep.

    Thread Starter dasigna

    (@dasigna)

    … so that much to the great new block editor … ;/

    anyway: there are two plugins that seem to be involved when the error occurs.
    – CF7
    Image Comparison

    with both (or only one) active the errors occur – without theres neighter errors nor inline injection of wp js (edit: o.k. partly, but much less). regardless whether AO is advised to also aggregate inline js or not…

    so far at least. have to check it on live site again.

    • This reply was modified 3 years, 9 months ago by dasigna.
    Thread Starter dasigna

    (@dasigna)

    … back on the hunting track too here.

    meanwhile tested on staging and have to confirm it has nothing to do with CF7 obviously.
    regarding some blocks thing too as the culprit that throws a lot of primarily backend js … and gives tons of errors with AO or only one, depending on settings.
    and yes, completely rebuildt the page with block editor lately, using generateblocks and toolset.

    lately back to practically activating everything in AO including ‘aggregate inline js’, ‘add try catch block’ and ‘minify excluded css and js’ which gives me one last (mentioned) error. (not including inline js throws up to 16)

    excluded scripts: seal.js, js/jquery/jquery.js, js/jquery/jquery.min.js, views-frontend.js, toolset-common-es-frontend.js

    error from console (detected at line:1):

    1 ... || document.write( '<script src="https://xxx/wp-includes/js/dist/vendor/wp-polyfill-element-closest.min.js?ver=STAGING-2.0.2"></scr' + 'ipt>' );</script> <script id='wp-api-fetch-js-after'>wp.apiFetch.use( wp.apiFetch.createRootURLMiddleware( "https://xxx/wp-json/" ) );
    2 wp.apiFetch.nonceMiddleware = wp.apiFetch.createNonceMiddleware( "9417a9fcb2" );
    3 wp.apiFetch.use( wp.apiFetch.nonceMiddleware );
    4 wp.apiFetch.use( wp.apiFetch.mediaUploadMiddleware );
    5 wp.apiFetch.nonceEndpoint = "https://xxx/wp-admin/admin-ajax.php?action=rest-nonce";</script>

    didnt find the bad guy yet … but anyway wondering what all this js that is visible without AO has to do within source code. youre able to see it in provided url.

    still hunting … but running out of ideas.

    Thread Starter dasigna

    (@dasigna)

    … same time here – so time to ditch off work for now, really ??

    tomorrows another day. ill leave it as it is meanwhile and also will see again what the new day might bring.

    wait for your response, thanks so far.

    Thread Starter dasigna

    (@dasigna)

    …!?

    so you are saying this error is all due to CF7??? no CF7 – no headache?
    strange – had already disbled it with no effect…

    anyway – can’t leave this as it is! 77 requests in comparison to 22 without ‘wpincludes’. thats crazy!

    Thread Starter dasigna

    (@dasigna)

    changed to the better, so the rating has been revised.
    keep it up and dont step back ??

    Thread Starter dasigna

    (@dasigna)

    hi jan,

    sounds good. love developers that listen ??

    settings in one place
    completely disagree…
    if one has only three plugins that spread their settings all over it might already get totally confusing. if they all have them in their own sub-item under ‘settings’ you’ll find them always and dont have to fiddle around which settings belong to which plugin in doubt. separated settings pages are way clearer!

    and remember – a dedicated settings page might give you the opportunity to place hints for your other plugins without too much distraction ??

    • This reply was modified 4 years ago by dasigna.
    • This reply was modified 4 years ago by dasigna.
    • This reply was modified 4 years ago by dasigna.
    Thread Starter dasigna

    (@dasigna)

    o.k. short breakdown.

    while i cant neighter speak for other users nor for the majority, i’l try to point out my point of view towards the behaviour of presenting free plugins…

    general

    first: “Products of devowl.io” checkbox – used to be there, but obviously no longer the case. so nothing to deactivate.

    dont want to go too deep into this, as every developer should have his own basis of how he presents his products and advertises other ones.
    but for sure in a free plugin this should not be obtrusive at all in any way.
    i dont want random popups or tootips (whatever) appear randomly in different and unexpected places. and for sure never ever for clients and their users asking me whats going on there. -> lately ditched off your pluging in testing environment just before buying the pro because of that.

    a developer that has trust in his product should not have the urge to force anyone into anything.
    already abandoned several plugins because of comparably behaviour – amongst others some infamous seo plugin. i want to keep my backend clean. at least not ‘spammed’ by anything i didnt made myself.

    upsells

    right. yeah – why not?
    but dont make them pop up randomly and even not in unexpected places.
    if your plugin convinces me and i need to have more than the free folders i’ll go and buy the pro anyway. because its worth it and i want for sure to honour your work.
    those in opposite who want everything for free wont even buy it because of your desperate ads.

    cross-sells

    i buyed the pro and you plugin searches my page for others you might have a replacement too? come on whats this? did i ask you to do so? is this gentlemans behaviour?
    this for sure is complete bullshit. sorry. what else are you spying for?
    gdpr compliance in sight?
    absolutely nogo!

    so what

    first: put the settings of your plugin in one place – dedicated subfolder under main settings. done. no searching here and there, all to be found where it belongs to – including deactivation of “buing reminders” and “calling home” options.
    and for gods sake you may put your informations about other services you provide into that page. but nowhere else. period.

    behaviour like the one youre showing lately should not appear at all imho.

    provide something for free if you wish to. even use it as a jump start for pro version. no problem with that at all. but stop enforcing anything in obtrusive manners.

    the list of already abandoned plugings because of this is quite long meanwhile (at least on my side) – i dont want to add another one.

    i already have a handsome number of pro licenses of your plugin up and running also. so i know it and i dont want to be bugged by it.

    Thread Starter dasigna

    (@dasigna)

    hi,

    referring to the free version here.
    using both. both bring up the same messages.

    as for the other question: i think you will know best what little bluish tooltips appear under certain conditions in which areas… right?

    no good practise and unwanted anyways. just stop doing so.

    nice weekend ??

    Thread Starter dasigna

    (@dasigna)

    TADA! ??

    tried immediately, and yes – works like a charm!
    some tweaks to dates and works as intended.

    many thanks for this quick reply and the direct solution. makes me happy.

    probably i might return with another challenge ??

    best regards.

    Thread Starter dasigna

    (@dasigna)

    yeah, thanks. clarifies.
    nothing more than i thought for myself and nothing unknown ??

    what bothers me ist the fact that hostings guys are so concerned …

    Thread Starter dasigna

    (@dasigna)

    thanks again. works of course.

    but as i discovered in addition: theres no extra HTML tag if the field is set to a simple text field. the tag only appears when its wysiwyg.

    great thing. who needs YST when there is TSF? ??

    • This reply was modified 4 years, 5 months ago by dasigna.
Viewing 15 replies - 1 through 15 (of 106 total)