Docs

[Brian B]

Hmm I don’t know if it’s related to this (http://theme.co/x/member/forums/topic/revolution-slider-bug-with-wordpress-multisite/) but I’m seeing this error on all pages as well…

In Chrome:
Uncaught TypeError: Cannot read property 'length' of undefined

In Firebug:
TypeError: e is undefined

There’s not any additional 3rd party plugins besides what’s required by X theme. The latest versions of the theme and related plugins installed.

Revolution Slider: Version 4.2.5
Visual Composer: Version 3.7.4
X-Shortcodes: Version 2.0.9
X-Theme: Version 1.8.0

I’m using the Integrity light child theme, installed according to the documentation.

I’m also seeing a console.log entry of ‘hey’ on the home page with the slider.

I also tried viewing the site with Rev slide and visual composer off and still saw the errors.

Here is the test link:
http://superiorhikingshuttle.test-sites.bsquared-tech.com/

Thank you,
Brian

[Brian B]

I’m also having an issue when I set the Portfolio URL:

This may or may not be related…

The portfolio works if I manually set up a portfolio page. But if the manually created portfolio page matches the URL for the Portfolio in the customizer, it breaks and the following error is logged…

PHP Warning: in_array() expects parameter 2 to be array, string given in /Users/username/web/example.com/public_html/wp-content/themes/x/framework/views/global/_portfolio.php on line 87, referer: http://example.dev/

But it’s a bit annoying because if the manually created portfolio page is setup, the URLs do not match properly, individual portfolio items would have the slug from the Customizer, not the URL of the manually created portfolio page… Hopefully this makes sense…

[Kory]

Hey Brian,

Thanks for writing in and we’re sorry that you seem to be experiencing some issues. The hey in the console is definitely something in Revolution Slider’s code, not sure why it’s there, but it’s not hurting anything. As far as the length error is concerned, can you please try deactivating the plugins you’re utilizing right now one by one to see if one of them is causing the problem? We can’t replicate this error locally or on our demo installations, so there has to be something unique about your setup that is causing this.

Regarding the portfolio setup, if you haven’t had a chance to read through the release notes in the sticky post at the top of the forum yet, definitely do as setup for this feature is explained in detail there (the following is taken directly from that article):

Finally, the last thing you’ll need to make sure you do is set your Portfolio Slug in the Customizer to something different than the slug your base portfolio page is set to. For example, if you have your portfolio setup at mydomain.com/my-portfolio/, then do not use my-portfolio as the slug in the Customizer. Instead, use something like my-portfolio-item in this field. This is a reality of working with multiple portfolios via a page template in that this slug must be set as a global across all of your portfolio items, and it must not match any of your portfolio index pages. Keep this in mind if you have multiple portfolios as well. Let’s say you have two portfolios setup at mydomain.com/my-first-portfolio/ and mydomain.com/my-second-portfolio/, if your portfolio slug in the Customizer is set to my-portfolio-item then all portfolio items will be listed out as mydomain.com/my-portfolio-item/title/ when you click through to them regardless of which portfolio is their “parent.” Simply remember that your slug will be used across all posts no matter how many portfolios you setup on your site.

Let us know when you have a chance!

[Brian B]

Excellent, thanks for the detailed response.

That makes sense about the portfolio setup now.

Well the only plugin I have besides those required by X theme is:

“Contact Form 7 Datepicker”
https://github.com/relu/contact-form-7-datepicker/

And you were correct, deactivating this plugin does stop the error. Hmm. There must be some sort of javascript conflict… I’m digging in further. Any additional insight would be appreciated.

We need date fields on our reservation form.

We have since deployed the site despite the errors it has been working well.

Home

[Kory]

Hey Brian,

Thanks for writing in! I’m glad to hear that you’ve isolated the source of the issue. Regretfully, due to our support policy which states that we do not support third party plugins, we will not be able to look into this any further since it appears to be a problem with the plugin and not the theme. You will need to address this particular issue with the plugin developer (which you should be able to easily do by opening up a new issue on the GitHub page that you linked to).

Thanks!

[Author]

Posts