malosch

Update:
As it turns out everything was fine with WP, the theme, plugins, as well as folder and file permission on the server. The issue was the ModSecurity firewall on the server which all of the sudden started blocking post.php from being executed (haven’t found out yet why that happened). Anyway, clearing the file post.php from the firewall fixed the issue.

Just reporting this here in case anyone runs into a similar issue.
Closing this thread for good now.

Thanks everyone, especially @otto42

Thanks for your input @otto42. What surprises me most is that everything stopped working from one day to another. But there were no WP updates, no server changes, no theme updates, nothing. I know something must have happened in the background somewhere to cause that issue, I just have no clue what. At least the site still works, for now, I just can’t make any edits at the moment.

Anyhow, I’ll close this thread for now and reach out to the theme authors. Will report back as soon as the issue is resolved.

Hi,

Thanks for the pointer. I downloaded the error log and the last entries are below.

[27-Mar-2019 20:29:37 UTC] PHP Warning:  include_once(/home/devchoco/public_html/wp-content/themes/bridge/includes/qode-fallback-helper-functions.php): failed to open stream: No such file or directory in /home/devchoco/public_html/wp-content/themes/bridge/theme-includes.php on line 15
[27-Mar-2019 20:29:37 UTC] PHP Warning:  include_once(): Failed opening '/home/devchoco/public_html/wp-content/themes/bridge/includes/qode-fallback-helper-functions.php' for inclusion (include_path='.:/opt/alt/php72/usr/share/pear') in /home/devchoco/public_html/wp-content/themes/bridge/theme-includes.php on line 15
[27-Mar-2019 20:29:37 UTC] PHP Warning:  require_once(/home/devchoco/public_html/wp-content/themes/bridge/framework/lib/qode.welcome.page.php): failed to open stream: No such file or directory in /home/devchoco/public_html/wp-content/themes/bridge/framework/qode-framework.php on line 2
[27-Mar-2019 20:29:37 UTC] PHP Fatal error:  require_once(): Failed opening required '/home/devchoco/public_html/wp-content/themes/bridge/framework/lib/qode.welcome.page.php' (include_path='.:/opt/alt/php72/usr/share/pear') in /home/devchoco/public_html/wp-content/themes/bridge/framework/qode-framework.php on line 2
[27-Mar-2019 20:30:13 UTC] PHP Warning:  require_once(/home/devchoco/public_html/wp-content/themes/bridge/framework/lib/qode.welcome.page.php): failed to open stream: No such file or directory in /home/devchoco/public_html/wp-content/themes/bridge/framework/qode-framework.php on line 2
[27-Mar-2019 20:30:13 UTC] PHP Fatal error:  require_once(): Failed opening required '/home/devchoco/public_html/wp-content/themes/bridge/framework/lib/qode.welcome.page.php' (include_path='.:/opt/alt/php72/usr/share/pear') in /home/devchoco/public_html/wp-content/themes/bridge/framework/qode-framework.php on line 2
[27-Mar-2019 20:30:50 UTC] PHP Warning:  require_once(/home/devchoco/public_html/wp-content/themes/bridge/framework/lib/qode.welcome.page.php): failed to open stream: No such file or directory in /home/devchoco/public_html/wp-content/themes/bridge/framework/qode-framework.php on line 2
[27-Mar-2019 20:30:50 UTC] PHP Fatal error:  require_once(): Failed opening required '/home/devchoco/public_html/wp-content/themes/bridge/framework/lib/qode.welcome.page.php' (include_path='.:/opt/alt/php72/usr/share/pear') in /home/devchoco/public_html/wp-content/themes/bridge/framework/qode-framework.php on line 2
[27-Mar-2019 20:30:55 UTC] PHP Warning:  require_once(/home/devchoco/public_html/wp-content/themes/bridge/framework/lib/qode.welcome.page.php): failed to open stream: No such file or directory in /home/devchoco/public_html/wp-content/themes/bridge/framework/qode-framework.php on line 2
[27-Mar-2019 20:30:55 UTC] PHP Fatal error:  require_once(): Failed opening required '/home/devchoco/public_html/wp-content/themes/bridge/framework/lib/qode.welcome.page.php' (include_path='.:/opt/alt/php72/usr/share/pear') in /home/devchoco/public_html/wp-content/themes/bridge/framework/qode-framework.php on line 2

Not sure what to do with this though. WP, bridge theme, and all plugins are up to date.

*EDIT* Tried to disable all plugins and enabling them one by one, no difference. Back to Google looking for other threads with similar issues. Any help or pointers in the meantime are much appreciated.

Thanks.

• This reply was modified 5 years, 11 months ago by malosch.

Hi,

Disconnecting and reconnecting Square did the trick. However, I wonder why that is and if there is a way to prevent this issue from happening again?

As for the mixed content warning, thanks for the hint ?? I appreciate that. I’ll work on fixing that issue now.

Thanks,
Markus

@dougaitken,
The support ticket is submitted and linked to this forum thread.

Thanks,
Markus

Hey @dougaitken,

Will do.
Would be great if we can solve that soon as Christmas is approaching fast and we’d love to have the store up and running by the end of November ??

Thanks.

Hi,

No problem at all ??

Below is the log message.

11-14-2018 @ 01:33:21 – ====Start Log November 14, 2018 1:33am====
Retrieving Merchant
====End Log November 14, 2018 1:33am (0.02)====

11-14-2018 @ 01:33:21 – ====Start Log November 14, 2018 1:33am====
Retrieve Business Locations
====End Log November 14, 2018 1:33am (0)====

11-14-2018 @ 01:38:06 – ====Start Log November 14, 2018 1:38am====
Retrieving Square Categories
====End Log November 14, 2018 1:38am (0)====

11-14-2018 @ 01:38:07 – ====Start Log November 14, 2018 1:38am====
Retrieving a Square Product for: fe43c4ea-d28a-4638-aa66-5a05c953bfb3
====End Log November 14, 2018 1:38am (0.02)====

11-14-2018 @ 01:38:07 – ====Start Log November 14, 2018 1:38am====
not_found – NotFound
====End Log November 14, 2018 1:38am (0.02)====

11-14-2018 @ 01:38:07 – ====Start Log November 14, 2018 1:38am====
Creating Square Base Product from: 16734
====End Log November 14, 2018 1:38am (0)====

11-14-2018 @ 01:38:11 – ====Start Log November 14, 2018 1:38am====
Updating Square Item Image for: db4f91ad-7af0-4989-b9e1-75a305a95afd
====End Log November 14, 2018 1:38am (0.07)====

And yes, I have gone through the troubleshooting. I will do so again tomorrow just to be on the save side.

Thanks

Check this thread, that solved the issue for me. https://www.ads-software.com/support/topic/mobile-touch-navigation/

You can also put the code in your CSS file. That’s what I ended up doing.

Thanks for the quick reply. And you’re right, the APA style handles long author lists like that ?? https://owl.english.purdue.edu/owl/resource/560/06/

My bad. Here I was using this citation style for years and never came across this particular scenario. Thanks again though!

Cheers,
Markus

Hi all,

Found a solution to prevent the browser from triggering navigating to the next/previous sides when using the touchpad. The solution is the position of e.preventDefault(); (see below).

_this.on('mousewheel wheel DOMMouseScroll MozMousePixelScroll', '.owl-stage', _.throttle(function(e) { // attaching mousewheel to .owl-stage and using throttling from underscore.js to prevent scrolling events from firing too often
																		//console.log(e.originalEvent.deltaX + " | " + e.originalEvent.deltaY); // debugging scroll distances
																		if(e.originalEvent.deltaY < -35 || e.originalEvent.deltaX > 35) { // condition to trigger carousel to go to next item
																				console.log("trigger NEXT"); // log in console for debugging
																				_this.trigger('next.owl'); // trigger carousel to go to next item
																		} else if (e.originalEvent.deltaY > 35 || e.originalEvent.deltaX < -35 ) { // condition to trigger carousel to go to prev item
																				console.log("trigger PREV"); // log in console for debugging
																				_this.trigger('prev.owl'); // trigger carousel to go to prev item
																		} else {
																				// do nothing
																		}
																}, 150)); // set throttling to 150ms
																_this.on('mousewheel wheel DOMMouseScroll MozMousePixelScroll', '.owl-stage', function(e) { //
																		e.preventDefault(); // prevent default event from being triggered -> prev/next screen in browser
																});

Essentially, the _throttle() function from underscore.js was preventing e.preventDefault() from triggering properly, which is needed to prevent the browser to interpret swipe gestures on the carousel as an attempt to navigate pages. Therefore, we can exclude e.preventDefault() in the function navigating the carousel, and create a new function specifically for e.preventDefault() right after the carousel navigation has been completed.

Hope that makes sense ??

Hi,

I was able to implement jquery.mousewheel.js to enable mouse wheel/trackpad navigation of the carousel.

Before sharing the code and what I have done, beware that there is still a bug. When scrolling horizontally on the trackpad to navigate between items, browsers interpret that as a gesture and go to the prev/next page. I am aware that this is outside of the scope of this thread but I will report back when I have found a solution to this.

Here’s what I’ve done to add mouse wheel/trackpad functionality to the carousel.

1. Added jquery.mousewheel.js
2. Added https://underscorejs.org/ to be able to prevent scrolling events from firing too often.
3. Added the following code to the class-carousel-slider-script.php file inside the if (jQuery().owlCarousel) { statement

_this.on('mousewheel wheel DOMMouseScroll MozMousePixelScroll', '.owl-stage', _.throttle(function(e) {
																		if(e.originalEvent.deltaY < -4 || e.originalEvent.deltaX > 4) { // condition to trigger carousel to go to next item
																				console.log("trigger NEXT"); // log in console for debugging
																				_this.trigger('next.owl'); // trigger carousel to go to next item
																		} else if (e.originalEvent.deltaY > 4 || e.originalEvent.deltaX < -4 ) { // condition to trigger carousel to go to prev item
																				console.log("trigger PREV"); // log in console for debugging
																				_this.trigger('prev.owl'); // trigger carousel to go to prev item
																		} else {
																				// do nothing
																		}
																		e.preventDefault();
															}, 150)); // set throttling to 150ms

• This reply was modified 7 years, 3 months ago by malosch.
• This reply was modified 7 years, 3 months ago by malosch.

Hi ??

So I tried to add the following code (as outlined here) inside the class-carousel-slider-script.php file:

_this.on('mousewheel', '.owl-stage', function(e) {																		
   //console.log("x: "+e.originalEvent.deltaX);																		
   //console.log("y: "+e.originalEvent.deltaY);																		
   if(e.originalEvent.deltaX > 100) {																				
      _this.trigger('next.owl');																		
   }																		
   if(e.originalEvent.deltaX < 100) {																				
      _this.trigger('prev.owl');																		
   }																		
   e.preventDefault();
});

I added the code right after the if (jQuery().owlCarousel) { statement inside the jQuery(document).ready(function ($) { function.

Using console.log(), I can see the mouse wheel values coming in steadily, so the function triggers properly and the values look good.
However, triggering next.owl and prev.owl doesn’t seem to work. The carousel always moves to the left, despite trying out different threshold values, or only using either next.owl or prev.owl in the code above. Sometimes, the carousel makes a single motion to the right but immediately moves to the left afterward. Based on that behavior, I assume something is overwriting my command or I am not using the correct command to control the carousel.

Any idea what I need to change to make the carousel respond properly to the input of a mouse wheel?

Any help or pointers are much appreciated!

Thanks ??
Markus

• This reply was modified 7 years, 4 months ago by malosch.
• This reply was modified 7 years, 4 months ago by malosch.

Hey Sayful,

Worked like a charm ?? Thanks for pointing me towards the right file.

And yeah, if you are adding more features in the future I think this might be a good option to add to the WP backend. And in case you don’t add it, I’ll just keep adding the one line of code everytime the plugin updates. Will be a bit tedious but not too bad.

In case anyone else wants to include this for their carousel, follow Sayful’s description and simply add stagePadding: 150, right after if (jQuery().owlCarousel) { _this.owlCarousel({ inside the public function inline_script() function.
You’ll find other options inside this if statement, such as nav, dots, margin, loop, etc. Just add it right there.

Thanks again Sayful

Hi,
So I had some time to look into the plugin as well as Owl Carousel 2 (which your plugin is drawing from) and I found the center: true; option. See https://owlcarousel2.github.io/OwlCarousel2/demos/center.html

The first example on the site is exactly what I am looking for – showing parts of the next picture to visually indicate that there is more content.

Any change that you’ll implement this option in future iterations of the plugin? And can you give me a pointer what file I’d need to change in your plugin to enable that option? I did some digging around in the plugin files but couldn’t fin the right file/spot.

Again, any help or pointers are appreciated ??

Thanks!