Home › Forums › Weaver and Plugin Interaction › VelocityPage Plugin Reference Error
- This topic has 7 replies, 3 voices, and was last updated 7 years, 11 months ago by
Weaver.
-
AuthorPosts
-
July 3, 2015 at 13:36 UTC - Views: 1 #17987
DRWoods
ParticipantGreetings,
I’m told by the support team over at VelocityPage (a drag-and-drop landing page builder) that the reason that I encountered issues when trying to add custom CSS to the page is due to the following error:“ReferenceError: Can’t find variable: wvrxEndOpts”
Is anyone familiar with this error? I searched the forum but didn’t see any discussions on this one. I’ve since deactivated the plugin as I’m no longer using it, however, I hope to reactivate it if there is a solution to this problem.July 3, 2015 at 16:47 UTC #23147scrambler
Moderatoryou may want to clarify which theme you are using as well as how you where trying to add CSS and what for.
Weaver theme have their own location to add custom CSS rule for the theme.
On weaver II (pro) it is in Advanced opions > HEad Section > Custom CSS Rule box
In Xtreme, in Main options > Fonts & Custom > Custom CSS Rule box
July 3, 2015 at 18:13 UTC #23148Weaver
KeymasterThis seems to be the same issue as the “Formidable Forms”. The plugin is generating a page that is not using a standard Weaver Xtreme header.php reference.
I don’t think there is a solution to this issue.
July 3, 2015 at 22:35 UTC - Views: 1 #23149DRWoods
ParticipantThank you all for the responses.
@scrambler: I’m using the Weaver Xtreme theme but the CSS was being added from within the VelocityPage plugin. It was supposed to allow me to change the look of the opt-in form itself but when added the default form would lose its background and show two bullet points regardless of what I put into the editor (see attached).@weaver: Yikes!July 4, 2015 at 00:05 UTC #23150scrambler
ModeratorTry to insert the CSS in Main options > Fonts & Custom > Custom CSS Rule box
If any issue, post back with the CSS in place, telling us what the CSS is and what it is for
July 4, 2015 at 14:30 UTC #23151DRWoods
Participant@scrambler: Well now it looks like there is another issue: I can’t even SAVE the page anymore. Prior to the previous issue, I was able to SAVE the page and then EDIT it. Neither one is an option now for some reason or another.
One important note: When I was able to edit the page, I added shortcode and CSS that would allow me to edit the opt-in form. The opt-in form was from the Double Opt-In Form Download (DOIFD) plugin. There seems to be a disconnect between VelocityPage, DOIFD, and Weaver Xtreme.July 4, 2015 at 16:34 UTC #23152scrambler
ModeratorIf your plugin option page does not work, there is really nothing we can do with that, you would need to speak to the plugin developer and ask him what is going on
July 4, 2015 at 19:09 UTC - Views: 4 #23153Weaver
KeymasterPart of the issue here is that there seems to be Weaver and TWO other plugins involved. It sounds like (but we can’t confirm for sure – I don’t think I’ve seen a link to the site that demos the problem) the plugins are somehow or another creating their own pages, bypassing Weaver’s generation of a page.
Weaver Xtreme is a pretty complex theme, and uses some more advanced methods to generate pages and sidebars. These are totally supported by WP, and within the WP specifications, and are intentionally designed by WP to support more advanced page and sidebar generation. However, these methods are not all that commonly used. We have seen in the past that many plugins assume that a theme will use only the most basic methods to generate pages and sidebars, and thus fail with Weaver. This is a failure on the part of the plugin, and not Weaver.
It is really not possible for us to acquire and become competent with the many plugins out there (other than a few very widely used plugins like WP Edit, WP SEO, or Woocommerce) . Certainly VelocityPage and DOIFD have not yet reached that stage.
-
AuthorPosts
- The forum ‘ Weaver and Plugin Interaction’ is closed to new topics and replies.