rcain
Forum Replies Created
-
I too am experiencing this FATAL error. Thanks for your response Paul – that makes sense. I will look further into a fix.
Thanks for the response Michelle. That explains it, but does not justify it, since as I explained, if I choose GA3 as primary THEN I can manually input the GA4 measurement ID and API key – you simply need to make THAT manual method available when setting up GA4 as primary, rather than over-complicating it with a flawed automation/use case. Hope that makes sense. Thanks again. Out.
Forum: Plugins
In reply to: [WooCommerce Stripe Payment Gateway] Action Required banner does not go awayHi Grigorij,
Thanks for the response.
I edited the db records directly as you suggested & it has indeed remedied the ‘visible’ issue. (There were actually a couple of similar erroneous messages. I used phpmyadmin from server CP since the wp phpmyadmin plugin is a bit of an unnecessary security risk).
Obviously this hasn’t fixed the underlying defect in woocommerce – any idea when the team there will be shipping an actual/tested fix?
Many thanks
Rob
Forum: Plugins
In reply to: [WooCommerce Stripe Payment Gateway] Action Required banner does not go awayI’d like to report, I too have this same issue, even after updating to woo 7.8.0 (so have others). have added a comment to that effect on the woo github issue mentioned above.
Just done some further tests and have some additional info to add + a hypothesis of cause: viz:
From the ‘white’ Instagram screen : Using browser FF > inspector > networks : can see that the call to:
https://www.instagram.com/graphql/query/?query_hash= … – is returning a 401 unauthorised. All other requests in page seem to respond fine.
AND:
connecting to the internet over a mobile wifi hotspot (instaad of my usual hardwired connection) – and everything works as expected!
So, my hypothesis is, that whilst testing and debugging the old version of the Smash Balloon plugin (which produced the horid Error 100 error from instagram) – i suspect I/we may have triggered instagram into (partially) BLOCKING our IP, due to too many unsuccessful attempts (on the old API). (Although i cant explain why it still didn’t work over Tor).
I’m HOPING that, instagram will eventually unblock our IP again after 48 hours or so. fingers crossed. will report back in the hope this thread helps other people with similar issue to understand whats going on.
- This reply was modified 2 years, 11 months ago by rcain.
I am experiencing the same issue. latest: WP V6.2.2 + Sucuri V 1.8.39 – sucuri dashboard showing:
141B26/05/2023 2:59 amwp-includes/images/crystal/license.txt 73.07K26/05/2023 3:00 amwp-includes/js/dist/block-directory.js 1.92M26/05/2023 2:59 amwp-includes/js/dist/block-editor.js 1.81M26/05/2023 3:00 amwp-includes/js/dist/block-library.js 529.03K26/05/2023 2:59 amwp-includes/js/dist/blocks.js 2.12M26/05/2023 2:59 amwp-includes/js/dist/components.js 184.47K26/05/2023 3:00 amwp-includes/js/dist/compose.js 217.72K26/05/2023 3:00 amwp-includes/js/dist/core-data.js 651.89K26/05/2023 2:59 amwp-includes/js/dist/edit-site.js 62.06K26/05/2023 3:00 amwp-includes/js/dist/element.js 29.33K26/05/2023 3:00 amwp-includes/js/dist/keycodes.js 25.54K26/05/2023 2:59 amwp-includes/js/dist/list-reusable-blocks.jsas being modified – whereas they have only just been installed from fresh copy of WP (from https://wordpress.org/download/ ). sucuri has also only just been installed for first time on this site.
- This reply was modified 2 years, 11 months ago by rcain.
HI @senols,
Thanks for the response. Yes, I tried the ‘Additional Context’ section – it does indeed insert extra ‘Additional context:’ clause, HOWEVER, it does not/cannot alter what has already been set up in the ‘Tone:’ and ‘Act As:’ clauses of the prompt.
Just for example, I might want a ‘Tone: Enthusiastic’ ‘Act as: Musician’ – but these aren’t available in the drop-downs, and attempting to enter them in the Additional Context’ clause is simply going to confuse it, since it will result in conflicting entries.
One possible solution, might be to implement an ‘Other…’ option value that allows free text input for ‘Tone’ and ‘Act as’ values (etc). (Alternatively, maybe a ‘None’ option for Tone and ‘Act as’ (etc!?), so that, ‘ ‘Additional Context’ values don’t conflict. Or, alternatively maybe add a wp user filter in the form & widget code such that we could ‘append’ our own custom options to the drop-downs. Or, even just a basic filter available on the final composed prompt, before it gets sent to ChatGPT would be helpful). Just some thoughts.
Does that make sense?
Best regards
- This reply was modified 2 years, 11 months ago by rcain.
done. with pleasure. 🙂
Forum: Plugins
In reply to: [Image Regenerate & Select Crop] more precise cropping of thumbnails onlyPS. as an alternative, is there any method of replacing JUST the thumbnail with a completely different image altogether (eg: a newly uploaded one, rather than one produced by cropping by plugin/wp)?
Thanks
Hi Jelena,
Thanks for that. Indeed I had checked there, but it didn’t seem to be effective. But your second note explains things – vis:
Shield menu > Config > Traffic > “Auto Expiry Cleaning” = 3
whereas
Shield menu > Config > Activity > “Auto Clean” = 7– and it was taking the greater of these two figures it seems for both Traffic Logs & Activity Logs retained.
Slightly confusing. But I now understand why. Thanks again 🙂
- This reply was modified 3 years, 7 months ago by rcain.
Forum: Plugins
In reply to: [Unlist Posts & Pages] Previous Post, Next Post Linksupdate:
I’ve fixed the issue by modifying your code slightly: vis:
file: /unlist-posts/class-unlist-posts.php ::
class: Unlist_Posts :function: post_navigation_clause :
line: 131 (approx):... // mod jrc 030621: fixup for visibility of other hidden whilst viewing hidden: // orig: if ( ( is_admin() && ! wp_doing_ajax() ) || in_array( get_the_ID(), $hidden_posts, true ) || empty( $hidden_posts ) ) { if ( ( is_admin() && ! wp_doing_ajax() ) || empty( $hidden_posts ) ) { // end mod jrc 030621: ...function: comments_clauses :
line: 207 (approx) :... // mod jrc 030621: fixup for visibility of other hidden whilst viewing hidden: // orig: if ( ( is_admin() && ! wp_doing_ajax() ) || in_array( get_the_ID(), $hidden_posts, true ) || empty( $hidden_posts ) ) { if ( ( is_admin() && ! wp_doing_ajax() ) || empty( $hidden_posts ) ) { // end mod jrc 030621: ...done: tested – all seems to work as required – ok
todo: i wonder if you could take a quick look at this and check there aren’t any undesirable side effects that I’ve overlooked. If all is OK with you, wonder if you could apply change to next release?Thanks again
Rob Cain
- This reply was modified 4 years, 11 months ago by rcain.
Hi there,
Thanks for that. Very helpful.
Just in case it helps anyone else, the current Hubspot quotas are set out here:
- https://legacydocs.hubspot.com/docs/faq/working-within-the-hubspot-api-rate-limits
- https://legacydocs.hubspot.com/apps/api_guidelines
I’m going to add some custom filters to your code so as to be able to override the default batch sizes and scheduler intervals etc – will be helpful to people i think. Only minor changes. Will publish here when I’ve tested them.
Best regards
- This reply was modified 5 years, 4 months ago by rcain.
i ended up going into browser inspector and ‘unhiding’ some of the panels on the initial sync screen, which in turn showed me a link, which in turn took me to the dashboard & settings page/url. now i am here, the plugin seems happy, and importantly i, the user, can see what is actually going on, plus, control the way the job runs, pause, resume, adjust the settings, whatever i should desire.
i will try and add a custom filter hook to your code to permanently enable this view of things, should it be desired – it is much more helpful like this,
in the meantime however, the issue of the ‘FAILED’ error message covering the progress bar and effectively ‘disabling’ the whole interface, and what triggered it, remains a mystery for the while. I’ll track it down.I have a good idea what it is.
Cheers
- This reply was modified 5 years, 4 months ago by rcain.
HI,
Thanks for your reply.
Yes, I realize all of that. But the hook is getting triggered (it seems) multiple times per order. Can you think why this might be?
Many thanks.
Hi there,
Thanks for the reply.
I do understand why it needs to be slow, over a big data set, if it is executing in the back-ground during trading hours. And thanks for explaining the reason.
However, I was hoping to shoot more records through, faster, by running it overnight (negligable user demand).
Could you tell me please – is the current API rate limit (and batch quota), a restriction set by Hubspot themselves? Or is it only for performance concerns of the local website?
Very many thanks.