You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your plugin works great for editing html-code in pages and posts. But I noticed today that it unfortunately interferes with the template editor of the Pods framework editor. Pods is an important framework used by thousands of builders to create custom post fields and relations. It includes an essential template coder. That code has its own syntax highlighting (see screenshot). When your plugin is activated, the Pods template code shows the same code twice, once in your syntax highlighting, and below that in it's own scheme. Both can be scrolled and edited but changes are not reflected in the other version and cannot not saved. Would it be possible for you to add to you plugin a way of selecting where it is active, and where not? I was really very happy with the syntax highlighting in the Gutenberg code screen, but this interaction with Pods renders it useless for the moment, I'm afraid...
The text was updated successfully, but these errors were encountered:
Your plugin works great for editing html-code in pages and posts. But I noticed today that it unfortunately interferes with the template editor of the Pods framework editor. Pods is an important framework used by thousands of builders to create custom post fields and relations. It includes an essential template coder. That code has its own syntax highlighting (see screenshot). When your plugin is activated, the Pods template code shows the same code twice, once in your syntax highlighting, and below that in it's own scheme. Both can be scrolled and edited but changes are not reflected in the other version and cannot not saved. Would it be possible for you to add to you plugin a way of selecting where it is active, and where not? I was really very happy with the syntax highlighting in the Gutenberg code screen, but this interaction with Pods renders it useless for the moment, I'm afraid...
The text was updated successfully, but these errors were encountered: