jjthornton
Forum Replies Created
-
Forum: Plugins
In reply to: [Multiple Columns for Gravity Forms] Load CSS and JS options not presentHi @mohit2002,
I see a possible area in the code that may be causing an issue. Can you please send a link to your form to the email address: gfmc@webholism.com, as I would like to confirm if your form is encountering the same behaviour.
Thank you.
Forum: Plugins
In reply to: [Multiple Columns for Gravity Forms] Load CSS and JS options not presentHi @mohit2002,
Thank you for pointing this out. Let me look into this and get back to you.
Can you tell me if you were using the features activated/deactivated by those checkboxes?
Thank you.
Hi @agepcom,
I hope that the update has resolved the admin issue for you, but let me know if not.
Not sure on why a more comprehensive multiple column solution is not part of the default Gravity Form offering. I am sure that they have their reasons. 🙂
Thanks for hanging in there and I hope that this little plugin goes some way to making your life a little easier. 🙂
@devnihil I was still having problems with the Fatal Allowed Memory issue up to 19.5.1. At this point I dug into the situation a little and realised it is due to a conflict with WordPress Persistent Login plugin. After removing the plugin, all was fine once more.
Thank you for all the work that the Yoast team put into developing this plugin.
@swb1192 Thanks for mentioning your own experience.
The site I am having issues with has 1 post, and 12 pages which have been created. I would be interested to know the plugins, and themes that your problem site is encountering, to be able to establish if there is overlap?
I too downgraded to 19.1 and the problem disappeared.
Please let me know if you are willing to compare installed plugins/themes.
Wishing you a great day.
Kind regards, jj 🙂
Many thanks for your response, and for the information. I fully understand that this issue is probably not particularly common, and I really appreciate you and your colleagues taking the time to point me in the right direction. 🙂
I will continue to tinker with the issue using the developer documentation link that you provided.
Wishing you and all at Yoast a fantastic week. 🙂
Kind regards.
Many thanks for getting back to me.
I wonder if you can advise me on how this may happen using the plugin as I confess to still being a little naive in the process flow of the Yoast code. I am looking to the yoast_indexable table and for a single permalink I am seeing two entries, one with an object_id defined and the other with a null value. From my manipulation of the database rows it appears that the entry with the null object id appears to actaully update the <meta> value for the og:image on the front end, but this does not get updated when the post is modified, the one with the object_id set to the post’s id value does. Please note that the two entries seem to also differ in their object types & sub object types; one shows
postandpage, the otherpost-type-archiveand the ACF custom post type definition.Is that of any use in understanding what may be the cause of this issue? Is there anything else I can do to merge these two entries?
Many thanks.
Hi @mikes41720,
Thank yo so much for taking the time for provide such an easy to follow guide of what to do, and I can happily report that I followed the steps you defined.
Sadly though, the process has not resulted in a change in the outcome. The og:image meta is still showing as the default URL on the front end and not picking up the custom image defined on the ACF page. Investigation shows that the _yoast_indexable table still does not have any data for the open_graph_ columns for the row that corresponds to the page in question.
Are you able to provide any information related to the files that I can look to, so that I can understand the process of modifying the _yoast_indexable table when an update is made on the backend? As specified this appears to be happening only for those pages that are the key post_type pages as defined in client ACF plugin.
Any further recommendations are appreciated.
Kind regards,
jjHi @maybellyne,
Thank you for your response.
I do not see any change in behaviour with plugins deactivated, those that I can and still reproduce the issue that is. The theme is also not available for deactivation, as the ACF functionality has been coded directly into it and the issue cannot be reproduced on an alternative theme. 🙁
What I have found is that the ACF pages show in the _posts table as post_type = page, and in the _yoast_indexable table in the object_type column as post-type-archive. When I update a problem ACF page, having updated the Yoast Social Media tab image, the _yoast_indexable open_graph columns do not appear to get updated. So while I see the change in the administrator area, I do not see this information reflected in the og:image meta on the front end. Can you recommend where I can look to understand how this linking occurs, and how I may be able to trace why this breakdown in behaviour is occurring for this small number of problematic pages?
Any help that you can provide is greatly appreciated.
Kind regards,
jjHi @wfadam,
Having followed your recommendations and also having contacted Siteground I am left in a similar situation. The cron jobs were not working even after using the WP Crontrol plugin and Siteground recommended that I use the procedure defined in https://my.siteground.com/support/cpanel/tutorials/wordpress/real-cron-job. This I have done. I have also set up a staging site in Wordfence Central account. The sad news is that I am still not able to see the scan working on the Siteground staging site. 🙁
Any other assistance that you can offer is appreciated.
Thank you in advance.
Hi @wfadam,
Your points are noted, and I had not seen that Siteground URL.
I will look at investigating and implementing your recommendations.
Thank you for taking the time to assist me, and hopefully I will bother you no more. 🙂
Take care and have a great week.
Kind regards.
Hi @wfadam,
Sorry to be a nuisance. 🙁
I have just sent the diagnostic report as requested. Please let me know if I can do anything more to be useful.
I greatly appreciate your time and assistance.
Kind regards.
Hi @wfadam,
I just wondered if this is something that you have been able to investigate?
If there is anything else that I can do my end to determine my inability to run scans on Siteground staging sites, please do not hesitate to ask.
Many thanks for your time and I wish you a wonderful day.
Kind regards.
Hi @wfadam,
I apologise for any misunderstanding that I may have introduced, but this situation continues. 🙁
I am happy to try any other recommendations that you may have, and I would appreciate any suggestions that the WF team can offer.
Thank you very much and wishing you a wonderful day.
Kind regards.
Hi @wfadam,
Did as you say, and that worked a treat. 🙂
Many thanks for your time, and wishing you a wonderful day.
Kind regards.