Forum Replies Created

Viewing 9 posts - 31 through 39 (of 39 total)
1 2
  • Author
    Posts
  • March 24, 2015 at 10:16 am in reply to: Additional in Hotspot text when using Image with Hotspot #416966
    GeorgLudwig

    Hi Ismael,

    thanks for that. Workaround does the trick actually. Elliotts workaround doesn’t limit on Image with Hotspots, so that the Tooltips everywhere are affected. So for those having the same problem:

    .av-image-hotspot .inner_tooltip {
    margin-top: -15px;
    }

    Georg

    March 22, 2015 at 11:59 am in reply to: Additional in Hotspot text when using Image with Hotspot #415939
    GeorgLudwig

    Hi ISmael,

    this is yet another workaround – I have a working one using CSS – I guess the main goal should be to correct the error, not to create workaround – right?

    Georg

    March 20, 2015 at 6:14 pm in reply to: Additional in Hotspot text when using Image with Hotspot #415444
    GeorgLudwig

    Just open the Debugger and uncomment my Custom-CSS which is:

    .inner_tooltip {
    margin: -20px 5px 5px 5px;
    }

    The heading moves down by those 20px. If You check the HTML-Code in the debugger for this Tooltip and remove the unnessecayr “<p></p>” right before the heading, then everything looks fine – so it’s definetely NOT the margin of the heading. Now let’s check the raw source code.You will find the following code for the Hotspot:

    <div class='av-image-hotspot_inner' style=' '>4</div><div class='av-image-hotspot-pulse' ></div></div><div class='av-image-hotspot' data-avia-tooltip-position='bottom' data-avia-tooltip-alignment='right' data-avia-tooltip-class='av-tt-xlarge-width av-tt-pos-below av-tt-align-right av-mobile-fallback-active av-permanent-tooltip-single main_color av-tt-hotspot' data-avia-tooltip='</p><h4>Markante <strong>Einsätze</strong></h4><p>

    Let’s translate the data-avia-tooltip’s beginning to real HTML:

    </p><h4>Markante Einsätze</h4>

    So, there is a closing paragraph on top of the heading – no idea, where You place the opening one. It’s of course the block we removed right before in the HTML-Debugger.

    Do You now see the problem ? I suggest it has to do with the

    ShortcodeHelper::avia_apply_autop($content)

    which is used in the image_hotspots.php (511).

    Regards,
    Georg

    March 19, 2015 at 6:13 pm in reply to: Additional in Hotspot text when using Image with Hotspot #414706
    GeorgLudwig
    This reply has been marked as private.
    February 13, 2015 at 9:59 am in reply to: Crawling Errors 500 #395564
    GeorgLudwig

    I added the entry into the robots.txt – the error currently does not appear anymore. So let’s wait and see – thx anyway

    Georg

    February 12, 2015 at 12:02 pm in reply to: Crawling Errors 500 #394913
    GeorgLudwig

    I’m quite aware of sporadical server errors, but as You can see in the error log even one error is obvious, which is the directory listing. As You can read in the referenced support thread at the beginning this is because google tries to scan the directory which should not occur. The question remains whether this is possible to inhibit by robots.txt.

    The other two errors regard the get_header() – as the page is loading quite regularly when opening it I do not suggest this to be a reproducable issue, but I though You’d perhaps seen this behaviour before for any kind of reason.

    The server error is indicated in the webmaster console as 1 error, but referenced by almost each page on the site.

    Regards,
    Georg

    February 11, 2015 at 5:48 pm in reply to: Crawling Errors 500 #394519
    GeorgLudwig

    In Webmaster-Tools the error appears in the first tab “Server Errors”

    In the log I have

    66.249.67.91 – – [08/Feb/2015:23:39:26 +0100] “GET /wp-content/themes/enfold/ HTTP/1.1” 500 0 “-” “Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)” “www.diva-heels.de”

    and
    [Sun Feb 08 18:45:16 2015] [error] [client 66.249.67.91] PHP Fatal error: Call to undefined function get_header() in /is/htdocs/wp1026082_MQOSW0RJLQ/www_diva/wp-content/themes/enfold/index.php on line 9

    [Sun Feb 08 18:45:33 2015] [error] [client 66.249.67.91] Directory index forbidden by Options directive: /is/htdocs/wp1026082_MQOSW0RJLQ/www_diva/wp-content/themes/enfold/framework/

    [Sun Feb 08 23:39:26 2015] [error] [client 66.249.67.91] PHP Fatal error: Call to undefined function get_header() in /is/htdocs/wp1026082_MQOSW0RJLQ/www_diva/wp-content/themes/enfold/index.php on line 9

    January 30, 2015 at 9:28 pm in reply to: Portfolio pagination with more than one category #388516
    GeorgLudwig

    I guess I understand – using the category on one page means filtering the current page – and it works correct as I see. A bit confusing. I’d expected, that – if I choose a category – all items are filtered by that category. And not only on the current page. Do You thing this is user friendly ? I gues a user would expect the same – if I choose a category, then all items are shown matching that category. But that would require reloading the missing ones which ist done as I see on pagination. Do You see a way to reflect the user expectance here, or do I have to display all items in order to get a meaningful result?

    Regards,
    Georg

    January 30, 2015 at 4:07 pm in reply to: Portfolio pagination with more than one category #388290
    GeorgLudwig

    Next mismatch:

    I open the same page and displays all Items – 8 pieces in two rows, pagination for page 1 and two. I choose another category consisting of 5 Items and it displays the category with only 1 row and 2 items – showing pagination. When I move to page #2 all 5 items are displayed correctly, but on page 2 ?!

    Georg

  • Author
    Posts
Viewing 9 posts - 31 through 39 (of 39 total)
1 2