Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hello,
When I activate Yaost module, I have a problem with page manager.
I create a variant:
- In the item "context" > I choose "node edit form"
- In the item "content" > I can't choose a content. The option in the region (exemple "center") is desactivate.
Can you help me please ?
Thank you.
Comment | File | Size | Author |
---|---|---|---|
#7 | yoast_seo-js_error-2625862-7-7.patch | 557 bytes | jorgegc |
Comments
Comment #2
thomas.leperou CreditAttribution: thomas.leperou commentedComment #3
thomas.leperou CreditAttribution: thomas.leperou commentedIndeed there is some issues with javascript (from Drupal 7.41, on simplytest.me with a pure fresh install).
Actually, on the front end Yoast give an issue :
ReferenceError: detectCKEditorInstances is not defined : yoast_seo.js:89:13
TypeError: a is null : yoast-seo.min.js:1:29967
This seems to be a minor issue for working with CKedtor.
On the backend, when we use Yoast in Page Manager with node_add or node_edit context, there is another bug :
TypeError: document.getElementById(...) is null : yoast_seo.js:231:10
This break the "add content" functionality of page manager (when working with a Panel variant).
Need fix and review, any volunteers ?
Comment #4
Niels de Ruijter CreditAttribution: Niels de Ruijter commentedThe first error is probably related to 2574277.
The second one I will be looking into, don't know what is causing that.
Comment #5
robertragas CreditAttribution: robertragas commentedDo you still have this issue?
Comment #6
robertragas CreditAttribution: robertragas commentedNo activity in 2 months so closing the issue. If you still have this issue you can reopen the ticket.
Comment #7
jorgegc CreditAttribution: jorgegc as a volunteer commentedHi guys, I am getting the same error (second one as described in #3) on node edit pages. Re-opening the issue and submitting a patch for review.
Comment #8
james.williams CreditAttribution: james.williams at ComputerMinds commentedI have found that ensuring I'm on the latest metatag module (7.x-1.14 at the time of writing) resolves the issue for me. I haven't tested, but given the discussion on #2653498-7: PHP notice when upgrading Metatag module, 7.x-1.8 may be sufficient.
Comment #10
robertragas CreditAttribution: robertragas commentedStill cannot reproduce the error but Jorge his patch looks good and doesn't break anything while I was testing , so if it should fix the issue for alot people i'm willing to let this one through.