krista06880
Forum Replies Created
-
Forum: Plugins
In reply to: [Autoptimize] Slow backend page savingBased on the lack of response from ET to this issue, they seem to be in no rush to resolve the problem. (They’ve also been touting how they’ve been making changes to optimize their code for speed.)
Since Divi continues to take 3 seconds to get to first paint (!), could you please help those of us who are using Divi who don’t have time to migrate to a faster theme?
I’d like to try to avoid having your recommended fix overwritten.
To avoid overwriting or your recommended change, do we do the following:
1. Create a blank init.php file
2. Add “// autoptimizeCache::clearall();” to the file, without the quotes
3. Add new init.php file to our Divi-child folder inside the directories: Divi-child/core/components/Thank you in advance for your kind assistance.
Forum: Plugins
In reply to: [Gutenberg] Conflicts with GrammarlyHiya Marius,
As someone who uses WP and benefits from all those who volunteer their time and effort, I appreciate your creation. So, thank you for your good efforts.
Since we do use WP for writing, I would urge Word Press developers to think about the advantages of a spell and grammatical check. It is central to the act of writing. And what is a blog? A tool for writing.
Grammarly helps keep writers from embarrassing ourselves online. What word processing app lacks grammar-check and spell-check these days?!? Seriously, name one (besides WP Gutenberg). Having zero grammatical review before publishing a blog post for all the world to see makes absolutely no sense to me. It flies in the face of logic.
Please think about UX.
As you prioritize development of WP, I urge WP developers to enable some kind of grammatical functionality. Grammarly should work in WP Gutenberg. Heck, it works in this interface as I type. It is a Chrome extension. Might there be a relatively easy fix that would enable it to work in WP? Given the critical importance of having that kind of functionality, has anyone looked into that?
At present, writers must copy/paste what they’ve written into an app where Grammarly does work such as Google docs or Gmail or Slack or Medium or Twitter or Facebook or LinkedIn.
Making more work for your users is generally not a good thing. (What would Steve Jobs say?) If you want writers to do their writing in WP Gutenberg, some might argue that it is wrong-headed to insist that we do it without a grammatical and spelling safety net.
(And, though I generally love advances in user interfaces, I have turned off WP Gutenberg. It made mincemeat out of the Divi builder experience.)
Thank you for your kind consideration.
- This reply was modified 5 years, 9 months ago by krista06880.
Hello Matt,
You are referring to the functions.php file of our theme, correct? I have the same question as the others here. I”m trying to figure out how to keep the plugin working after the Salesforce change.
Many thanks,
KristaForum: Plugins
In reply to: [AMP for WP - Accelerated Mobile Pages] AMP pages with critical issuesLike @verivera above, I am experiencing a critical issue when I test my home page at https://tgsus.com/amp/ The error returned is “Invalid layout property found in AMP tag” with the additional detail “The implied layout ‘CONTAINER’ is not supported by tag ‘amp-img'”
It occurs on line 518 and appears to involve the Image Module in Divi. In checking your framework: https://ampforwp.com/tutorials/article/amp-theme-framework-code-explained/ I don’t see any code that addresses the issue. I’m wondering if you can help get it resolved. It does appear that others here have had the same issue. Thank you.
Forum: Plugins
In reply to: [Gravity Forms Salesforce Add-on] AttachmentsI’d love to have the attachment functionality work in Salesforce so that ithat the file gets attached to the Lead Record that’s created. It could be used to enable candidates to submit resumes . . .
Also, for my wish list, I’d love there to be a way to bring in leads as Contacts, attaching them all to the same Company placeholder record, such as one entitled “Candidate Pool”. It saves us the trouble of having to covert the lead to a contact record.
I resolved the issue with the warming or error message.
The API isn’t pulling all the custom fields I’ve got set up for the form. I have checked and the connection to Salesforce is valid. I also have clicked “refresh”. Still it is displaying some fields I have deleted. Moreover, it doesn’t display fields I need that are on the form. The fields include URL, multi select pick lists and pick lists.
Please advise.
I resolved the warning issue by checking both boxes in advanced options in the widget settings:
I checked:
Enable AJAX
Disable script outputStill have the other questions above. Thanks!
— KB