Forum Replies Created

Viewing 30 posts - 61 through 90 (of 134 total)
  • Author
    Posts
  • in reply to: REPLICATING LAYOUT #860234

    That looks good Victoria. As these are all responsive, I’m at a bit of a loss as to what size images I should use as background.

    I have added the sections in 2 examples UNDERNEATH the masonry. Both have a border of 10px, both have bg colours so you can see any gaps:
    https://littlegemscountrydining.co.uk/code-test/

    1st – Colour section with layout elements in
    2nd – Just the layout elements
    Images are:
    1/4 = 352x705pixels & 704x1410px (yes – I see they don’t fit – not sure what to do there!
    3/4 = 1410×745

    I would like it to be full screen stretch, and all borders the same …and that they still look good when on mobile (equal borders all round)

    ps. I have used images INSIDE the sections, as I could not get background to show a fixed size
    Thank you!!
    Stevo :-)

    • This reply was modified 7 years, 2 months ago by Steve.
    in reply to: Resolving blurred images on Masonry #859832

    Thank you Yigit – any guidance on what sizes I should be opting for…?
    otherwise I’m flying blind…

    Stevo :-)

    (ps. I also note that this plugin is over a year old, and appears to have been abandoned. Do the images regenerated stay put if we uninstall this plugin after use?)

    in reply to: Resolving blurred images on Masonry #859326

    Hi John,

    Thank you – a test page (with the photos as described above) is here: https://littlegemscountrydining.co.uk/block/

    ps. Maybe it’s because I’m full-screening on a large Mac, but the bottom two images at 705×705 are easily very sharp. The others, no matter whart sizes I concoct, are always blurred – they shoudl be sharp.

    Stevo :-)

    in reply to: REPLICATING LAYOUT #859324

    Hi Rikard,

    The test page is here:

    The page I’m trying to emulate (with 1/4 & 3/4 widths) is here:
    https://www.oakmaninns.co.uk/

    Regards
    Stevo :-)

    in reply to: REPLICATING LAYOUT #859016

    Hi Rikard,

    Yes – I would love some help trying to achieve this. I would like to get that layout – probably using Masonry gallery, I would think…?
    Can you provide some CSS guidance..?

    Many thanks
    Stevo

    in reply to: SSL Enfold errors #825105

    TJ… Thank you, thank you!!! Resolved.
    Really appreciated :-)

    in reply to: SSL Enfold errors #825092

    Thank you:
    chequers-ampthill.co.uk/
    chequers-ampthill.co.uk/product/gift-voucher/

    • This reply was modified 7 years, 5 months ago by Steve.
    in reply to: Blurred Photos – WooCommerce Product Pages #791241

    Thanks Nikko. I’ll sit tight… :-)

    Superb! Thank you :-)

    Thanks Andy, have implemented this temporary fix.

    I’ve requested the ability to NOT install this as a modification for future releases of Enfold (or at least a ‘kill switch’), as there are many who don’t use Layerslider.

    Regards
    Stevo

    I appreciate ALL the work that’s going on to fix this behind the scenes, but I do hope very much that LAYERSLIDER can be separated from the theme PERMANENTLY in future updates. This is a real pain if you have more than one Enfold site.

    Stevo :-)

    Now added as a feature request here: https://kriesi.at/support/enfold-feature-requests/
    PLEASE VOTE FOR IT!

    • This reply was modified 7 years, 9 months ago by Steve.
    in reply to: LAYERSLIDER update issue is BACK! #768333

    Text from Wordfence as follows:
    Critical Problems:
    * The Plugin “” needs an upgrade ( -> 6.2.1).
    Update includes security-related fixes. http://codecanyon.net/item/layerslider-wp-the-wordpress-parallax-slider/1362246/changelog

    ..and needless to say, that link takes you to a blank page.

    Stevo

    in reply to: LAYERSLIDER creating issues with plugin updates #765767

    I just updated the Wordfence plugin, and got this feedback (always unpleasant). It appears to all be LAYERSLIDER related. Please excuse all the ***hidden***/ stuff – just for privacy:

    Warning: fopen(***hidden***/wp-content/themes/enfold/config-layerslider/LayerSlider/layerslider.php): failed to open stream: No such file or directory in ***hidden***/wp-includes/functions.php on line 4783

    Warning: fread() expects parameter 1 to be resource, boolean given in ***hidden***//wp-includes/functions.php on line 4786

    Warning: fclose() expects parameter 1 to be resource, boolean given in ***hidden***/wp-includes/functions.php on line 4789

    Warning: fopen(***hidden***/wp-content/themes/enfold/config-layerslider/LayerSlider/layerslider.php): failed to open stream: No such file or directory in ***hidden***/wp-includes/functions.php on line 4783

    Warning: fread() expects parameter 1 to be resource, boolean given in ***hidden***/wp-includes/functions.php on line 4786

    Warning: fclose() expects parameter 1 to be resource, boolean given in ***hidden***/wp-includes/functions.php on line 4789

    Warning: fopen(***hidden***/wp-content/themes/enfold/config-layerslider/LayerSlider/layerslider.php): failed to open stream: No such file or directory in ***hidden***/wp-includes/functions.php on line 4783

    Warning: fread() expects parameter 1 to be resource, boolean given in ***hidden***/wp-includes/functions.php on line 4786

    Warning: fclose() expects parameter 1 to be resource, boolean given in ***hidden***/wp-includes/functions.php on line 4789

    It updated OK, but doesn’t feel good!!

    ~

    I have also sent the following to Wordfence support:

    I received the multiple ‘WARNING’ text in the Wordfence update window after the recent update was complete.
    I have also attached a screenshot of the WARNING from Wordfence SCAN.

    PLEASE NOTE: You might be aware that there is an ongoing issue with Layerslider plugin in Enfold theme, which WORDFENCE had alerted users to. Nothing sinister amiss: Layerslider is bundled free with Enfold and sits dormant unless activated. The current problem is that it cannot be updated normally, it has to be pushed as a template update by ENFOLD. It should not be picked up by update scans. We’re currently awaiting a fix from the Enfold team. So, Wordfence is throwing up a Layerslider plugin update alert, but it’s blank – literally “”.

    My questions therefore, are:
    1. Are these warnings all related to LAYERSLIDER?
    2. Are they critical, or just warnings as the plugin/theme is not functioning correctly?
    3. Is there anything Wordfence can do about this alert – possibly to ignore it?
    4. have you heard anything from either Layerslider (https://kreaturamedia.com/) or Enfold (http://kriesi.at/)?

    Hope this helps!
    Stevo

    • This reply was modified 7 years, 9 months ago by Steve.
    in reply to: LAYERSLIDER creating issues with plugin updates #765478

    elames – I think we need to wait for the Enfold update, which Basilis said they are working on…

    I think that’s correct Basilis?
    Stevo :-)

    • This reply was modified 7 years, 9 months ago by Steve.
    in reply to: LayerSlider error #765096

    Hi Basilis,

    This is not entirely correct. I have a layerslider with a license, and this site has no problem running on PHP 5.6 whatsoever.

    I don’t feel convinced it is the PHP version.

    Regards,
    Stevo

    in reply to: LAYERSLIDER creating issues with plugin updates #765086

    PS: Just updated another Layerslider-related problem feed with this:

    I have just updated one of my sites to PHP 7.0, and am STILL getting this error message from a WORDFENCE scan (editied for privacy) :
    wp-content/themes/enfold/config-layerslider/LayerSlider/layerslider.php): failed to open stream: No such file

    FOR INFO: This Layerslider install is NOT activate or licensed – it just came with the theme’s last update.

    Something is definitely amiss other than the PHP.
    Can we look a little further into this please?

    in reply to: LayerSlider error #765085

    Rikard, this isn’t correct I think.

    I have just updated one of my sites to PHP 7.0, and am STILL getting this error message from a WORDFENCE scan (editied for privacy) :
    wp-content/themes/enfold/config-layerslider/LayerSlider/layerslider.php): failed to open stream: No such file

    FOR INFO: This Layerslider install is NOT activate or licensed – it just came with the theme’s last update.

    Something is definitely amiss other than the PHP.
    Can we look a little further into this please?

    Stevo

    in reply to: LAYERSLIDER creating issues with plugin updates #765080

    Just had an update from CODE CANYON stating that there is a LAYERSLIDER update
    So, I guess somewhere between LAYERSLIDER & ENFOLD, an update error for the plugin occured.

    Where LAYERSLIDER is licensed (as I have on one of my sites) – no issues.
    This only occurs where (it seems) LAYERSLIDER is dormant, or unlicensed – i.e. as is, as it came with the last time it was updated within the ENFOLD theme.

    I think WORDFENCE is just picking up the error.

    * ENFOLD * chaps – any clues/possible update…?
    Stevo :-)

    • This reply was modified 7 years, 9 months ago by Steve. Reason: Additional comments
    in reply to: LAYERSLIDER creating issues with plugin updates #764977

    kaj69 – it is the same thing, apologies!
    I found the same error code/text in WF.

    Await a response from Kriesi & crew…

    (…and YES, there are missing images for the default layouts)

    • This reply was modified 7 years, 9 months ago by Steve. Reason: update
    in reply to: LAYERSLIDER creating issues with plugin updates #764750

    Slightly different. My issue is the fact that unless Enfold provide an update to the LAYERSLIDER plugin regularly, it causes an issue when security programs (like WORDFENCE which I use) check for updates to plugins.

    At present, there seems to be no LAYERSLIDER update via the ENFOLD theme, which it came with, so the WORDFENCE constantly nags saying that an update is available, but nothing shows when you try to update.

    In fact, the WORDFENCE security showed as ‘updates to “” plugin‘ – in other words, blank!

    Any thoughts please Kriesi and crew..?
    Thank you :-)

    • This reply was modified 7 years, 9 months ago by Steve. Reason: spelling!
    in reply to: Dots instead of bar separators in main menu #751465

    Hi Nikko,
    Your help v much appreciated, but that didn’t do a thing!
    Any other thoughts?

    Stevo :-)

    in reply to: Dots instead of bar separators in main menu #748898

    Thanks for taking a look. Link added in PRIVATE :-)

    in reply to: Wordfence found a suspected malware in an Enfold .php file #740621

    All clear here :-)

    in reply to: Wordfence found a suspected malware in an Enfold .php file #740609

    I have temporarily substituted the bad URL for a good one in the html-helper.class.php file.
    Re-scanned with WORDFENCE – no problem.
    Not saying this is a 100% solution, but it will stop any poss blacklisting for now!

    in reply to: Wordfence found a suspected malware in an Enfold .php file #740583

    It can be a concern as Google can blacklist your site if it finds the link when crawling to index etc.

    in reply to: external iframe content for mobile responsive layout #717935

    I shall take it up with the 3rd party…

    Thanks for the time Nikko :-)

    in reply to: external iframe content for mobile responsive layout #717806

    Hi Nikko – appreciate your response, but unfurtunately this didn’t do anything.

    Any other thoughts, or can I suggest anything to the code originators…?

    Thanks again :-)
    Stevo

    in reply to: FULLWIDTH SLIDER not loading in IE8 #704389

    Thank you Basilis. I do 100% understand.

    (Please just take it off your list of compatible browsers – as clients will look there and expect the same!)

    Best wishes
    Stevo :-)

    in reply to: google maps, coordinates not fetched #669772

    My apologies: found the temporary functions.php workaround:
    https://kriesi.at/support/topic/content-element-google-maps/#post-656399

    Posted for anyone else stumbling on this!
    Thank you Enfold peeps :-)

    in reply to: google maps, coordinates not fetched #669762

    The update has NOT resolved the issue.

Viewing 30 posts - 61 through 90 (of 134 total)