EvsanDlg
Forum Replies Created
-
My system info is below. The theme Sydney 1.20 is active.
Thing to notice: i replaced foobox lightbox plugin with older version 1.0.8 and everything works fine now and lightboxes show up at site pages correctly. But this log shows that foogallery “thinks” that it is not installed (but sees it in plugins list, though).
By the way, I tried to deactivate Autoptimize plugin, cleaned caches etc before Foobox version rollback. This didn’t help.FooGallery version : 1.8.12
WordPress version : 4.3.20
Activated Theme : Sydney
WordPress URL : http://svetlanasima.ru
PHP version : 5.6.38
PHP GD : Loaded (V2)
PHP Open SSL : Loaded
PHP HTTP Wrapper : Found
PHP HTTPS Wrapper : Found
HTTPS Mismatch : None
PHP Config[allow_url_fopen] : 1
PHP Config[allow_url_include] : 1
Thumbnail Generation Test : http://svetlanasima.ru/wp-content/uploads/2017/04/IMG_20190423_175430-01.jpeg
Extensions Endpoint : https://raw.githubusercontent.com/fooplugins/foogallery-extensions/master/extensions.json?v=8FyXQ#wt@ptB
Extensions Errors : Nope, all good
Extensions :
Extensions Active : Array
(
[0] => default_templates
[1] => foobox-image-lightbox
[2] => albums
[3] => foobox
)Gallery Templates : Array
(
[0] => default
[1] => image-viewer
[2] => justified
[3] => masonry
[4] => simple_portfolio
[5] => thumbnail
)Lightboxes : Array
(
[foobox] => FooBox (Not installed!)
)Settings : Array
(
)Active Plugins : Array
(
[0] => autoptimize/autoptimize.php
[1] => black-studio-tinymce-widget/black-studio-tinymce-widget.php
[2] => comet-cache/comet-cache.php
[3] => contact-form-7/wp-contact-form-7.php
[4] => fast-social-share-buttons/fss-buttons.php
[5] => foobox-image-lightbox/foobox-free.php
[6] => foogallery/foogallery.php
[7] => google-analytics-dashboard-for-wp/gadwp.php
[8] => lightbox-photoswipe/lightbox-photoswipe.php
[9] => pagination/pagination.php
[10] => redirection/redirection.php
[11] => ricg-responsive-images/wp-tevko-responsive-images.php
[12] => shortcodes-ultimate/shortcodes-ultimate.php
[13] => siteorigin-panels/siteorigin-panels.php
[14] => so-widgets-bundle/so-widgets-bundle.php
[15] => sydney-portfolio/sydney-portfolio.php
[16] => tinymce-advanced/tinymce-advanced.php
[17] => types/wpcf.php
[18] => wordpress-seo/wp-seo.php
[19] => wp-posts-carousel/wp-posts-carousel.php
[20] => wp-smushit/wp-smush.php
)- This reply was modified 6 years, 8 months ago by EvsanDlg.
I have the same issue after Foobox update to 2.7.5 from 1.~something. I didn’t updated for a long time. And now I blame myself for doing this.. My entire foreground site crashes in white page as far as admin page of the plugin does.
FooGallery-Version : 1.8.12
WordPress-Version : 4.3.20
PHP-Version : 5.6.38Спасибо. Однако проблема связана с возвратом на страницу оформления заказа до совершения оплаты, а не после
Forum: Plugins
In reply to: [Яндекс.Касса для WooCommerce] Нет в настройках woocommerce 2.6.6У меня тоже нет Яндекс.Кассы в списке шлюзов.
Плагины активированы: WooCommerce 2.6.14, Яндекс.Касса 2.3.4. WordPress 4.7.2Forum: Plugins
In reply to: [Яндекс.Касса для WooCommerce] Нет в настройках woocommerce 2.6.6А какая проблема то была в итоге? У меня тоже нет Яндекс.Кассы в списке шлюзов.
Плагины активированы: WooCommerce 2.6.14, Яндекс.Касса 2.3.4. WordPress 4.7.2Actually, I’ve found the answer using wp_style_is() function. It tells if the style is registered, enqueued or have already been printed. So, using wp_deregister_style() and testing the state of ‘font-awesome’ with wp_style_is(), I’ve found, that the next lines work for sure:
function YOUR_THEME_scripts() { wp_dequeue_style( 'font-awesome' ); wp_deregister_style( 'font-awesome' ); } add_action( 'wp_footer', 'YOUR_THEME_scripts');But the question is: is it necessary to deregister the script at all, especially in the footer. I think no, because it is just an extra work for wordpress engine. But I may be wrong.
Moreover, do not deregister script if you want to use it just at another pages and dequeued it only from some pages using if(is_page(‘Some page’)) wrapping in YOUR_THEME_scripts() function.
The hook above won’t work, because this stylesheet’s enqueue-handler is added in action ‘wp_footer’, ‘not wp_enqueue_scripts’ (see line 25 in assets.php).
Thus, to dequeue it, you need to do this:function YOUR_THEME_scripts() { wp_dequeue_style( 'font-awesome' ); } add_action( 'wp_footer', 'YOUR_THEME_scripts');This will prevent SU from loading stylesheet from the CDN. I’ve already checked this.
Besides that, you need to deregister this stylesheet. It is registered in action ‘wp_head’ (see line 20 in assets.php). But I don’t know if it is necessary to deregister script using exactly ‘wp_head’, or ‘wp_footer’ is appropriate for this purpose (I don’t know how register works, is it global or not)?
Forum: Plugins
In reply to: [WP Posts Carousel] Sydney Theme problemsOk. I’ll keep this in mind)
Thank’s for your plugin!Forum: Plugins
In reply to: [WP Posts Carousel] Sydney Theme problemsSolved. The problem actually was in conflict with Sydney’s /sydney/js/scripts.js file, as author said.
The point is that sydney theme containes some OWL-related code in the file above. It is made so for maintaining Sydney’s pre-defined widgets like Sydney Testimonials Widget or Sydney Team Widget. Thus, /sydney/js/scripts.js once loaded, it overrides native OwlCarousel functions of owl.carousel.jsI’ve just commented all owl-containing lines in sydney’s script.js file. But it ruines maintainance of described widgets and I still don’t know how get both: WP Posts Carousel and Sydney’s carousel-based widgets
Forum: Plugins
In reply to: [WP Posts Carousel] Sydney Theme problemsI have the same problem with WP Posts Carousel plugin v.1.2.3 on my Sydney theme v.1.20.
By the way, sydney theme has some styles for .owl-* objects in it’s style.css file, but I’ve commented all of it. Carousel still not working. The problem definitely not in there.Then I’ve checked the front-end side of my website:
– Plugin’s owl.carousel.css and carousel’s template stylesheets and owl.carousel.js scrypt are loaded, html <script> with load() function of carousel’s parameter’s has its place just after carousel itself. I think just like it should be
– jquery.js v.1.11.3 and jquery.mousewheel.min.js v.3.1.12 libraries are loaded correctly as well
– html of carousel has a structure, containes all posts information that is expected (e.g. there are 2 “owl-item” divs with title,description etc.). But it is hidden!So, what I’ve found is that #wp-post-carousel div does not have the “owl-loaded” class. Adding this class makes “wp-posts-carousel-slide” elements visible with all containing posts and meta data as well.
It makes me think that for some reason when loading of this carousel is finished, some usefull event doesn’t trigger or makes it incorrectly.I hope, this information could be usefull fo catching the problem
My test page with WP posts Carousel is here: http://svetlanasima.ru/989-2/