Lodigame3.Makakuha ng libreng 700pho sa bawat deposito

Forum Replies Created

Viewing 15 replies - 1 through 15 (of 33 total)

Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Catchable fatal error when trying to install 7.1.1

Thread Starter iangeek

(@iangeek)

5 years, 12 months ago

Hi @kraftbj – sorry for delayed reply…

OK, so the site in question is one of many I manage, but its a single installation running on PHP 5.6 (FPM via Apache). No multi-site, but a LOT of plugins (its one of those sites that’s evolved over 5 years or so, so its getting a bit Frankenstein back there). However nothing too outrageous or esoteric. I’ll dump a full list back when I get a moment, indicating any premium ones that require network activation.

The site is very active on a daily basis, so its difficult to find an opportunity to do the standard plugin-by-plugin / vanilla theme rollbacks to debug, but I’ll give it a go.

I need to update both the PHP and the WP version (don’t worry, Classic Editor is already up and running as a pre-emptive! None of my clients like the block editor, so its already been installed for everyone), but I’m trying to make sure everything else is up-to-date first, and seeing what plugins I can do away with.

Anyway, I’ll try some more things, get a log of all thats active, and dump back here as soon as poss. Thanks for looking into this!

Cheers

Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Catchable fatal error when trying to install 7.1.1

Thread Starter iangeek

(@iangeek)

6 years ago

OK, I’ve identified the problem…

Line 2060 is as follows:

return array_unique( $active_plugins);

This is fine for PHP 7, but for older versions it looks like array_unique() needs a bit of a helper:

return array_unique( $active_plugins, SORT_REGULAR );

This fixed the issue and allowed me to install it, although it means I’ve had to edit the core. So not ideal.

Can you feed it back to the team please, and get that fixed for the next round of updates? Thanks!

Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Catchable fatal error when trying to install 7.1.1

Thread Starter iangeek

(@iangeek)

6 years ago

line 2060 appears to be the part that defines get_active_plugins()… Could it be an issue with wp_options / active_plugins ?

Forum: Plugins
In reply to: [Advanced Custom Fields (ACF?)] Image field not returning URL in archive loop following update to 5.7.8

Thread Starter iangeek

(@iangeek)

6 years, 1 month ago

Apologies for leaving this thread cold (rude of me) – good fix @mwarner1 . I ended up doing much the same as a workaround. Still don’t really know why it happened, but glad to know I wasn’t the only one.

Forum: Plugins
In reply to: [WP Instagram Widget] Instagram disabling JSON?

Thread Starter iangeek

(@iangeek)

6 years, 10 months ago

Yep, confirmed fixed. Sorry for false alarm. Just feared the worst as I know Instagram are playing around with the API stuff a lot at the moment. Saw a few others referencing it on Twitter too, but guess it was an isolated blip.

Forum: Plugins
In reply to: [WP Instagram Widget] Instagram disabling JSON?

Thread Starter iangeek

(@iangeek)

6 years, 10 months ago

Yep, looks like the old __a=1 JSON way of pulling the feed has now been nuked:

https://www.instagram.com/iangeek/?__a=1

… which then triggers the “invalid data” error ??

Forum: Plugins
In reply to: [WP Instagram Widget] Instagram has returned invalid data.

iangeek

(@iangeek)

6 years, 10 months ago

Pretty sure its the same as the issue I’ve described in my support post: https://www.ads-software.com/support/topic/instagram-disabling-json/

Forum: Plugins
In reply to: [WP Instagram Widget] Inconsistent 200 error with latest version

Thread Starter iangeek

(@iangeek)

6 years, 11 months ago

The problem seems to be *mostly* resolved for me also, although still crops up now and again. I suspect your theory is right Scott… possibly some throttling going on behind the scenes with their API (which may or may not be temporary). I’ll keep an eye though.

Your suggestion for the error handling would be good – some sort of cache of the most recent [however many is set in the plugin] x images, so rather than display a verbose error and bust templates, it just falls back to that instead.

Cheers for your ongoing work on this.

Forum: Plugins
In reply to: [WP Instagram Widget] Inconsistent 200 error with latest version

Thread Starter iangeek

(@iangeek)

6 years, 12 months ago

Hey Scott – OK, you ready for this one? I’ll skip ahead on the bits that don’t really add much to the story…


Array
(
    [headers] => Requests_Utility_CaseInsensitiveDictionary Object
        (
            [data:protected] => Array
                (
                    [content-type] => text/html; charset=utf-8
                    [cache-control] => private, no-cache, no-store, must-revalidate
                    [pragma] => no-cache
                    [expires] => Sat, 01 Jan 2000 00:00:00 GMT
                    [vary] => Cookie, Accept-Language
                    [content-language] => en
                    [date] => Wed, 21 Mar 2018 23:55:57 GMT
                    [set-cookie] => Array
                        (
                            [0] => rur=PRN; Path=/
                            [1] => csrftoken=rBgHQnY0L2gWEUiCS2XBMEub0V8b7jz6; expires=Wed, 20-Mar-2019 23:55:57 GMT; Max-Age=31449600; Path=/; Secure
                            [2] => mid=WrLxDAAEAAFMegV-pjax-HlqsUhc; expires=Tue, 16-Mar-2038 23:55:57 GMT; Max-Age=630720000; Path=/
                        )

                    [content-length] => 21390
                )

        )

    [body] => <!DOCTYPE html>
<html lang="en" class="no-js not-logged-in ">
    <head><meta charset="utf-8">
        <meta http-equiv="X-UA-Compatible" content="IE=edge">

        <title>
                  Page Not Found &bull; Instagram
                </title>

        
        <meta name="robots" content="noimageindex, noarchive">
        <meta name="mobile-web-app-capable" content="yes">
        <meta name="theme-color" content="#000000">
        <meta id="viewport" name="viewport" content="width=device-width, user-scalable=no, initial-scale=1, minimum-scale=1, maximum-scale=1, viewport-fit=cover">
        

        <link rel="manifest" href="/data/manifest.json">

Yadda yadda… whole load of HTML mark-up from Instagram error page leading up to…


    

	<h2>Error</h2>

        <p>Please wait a few minutes before you try again.</p>

Skip to the end until we’re back with the JSON…


        
    </body>
</html>
    [response] => Array
        (
            [code] => 429
            [message] => Too Many Requests
        )

    [cookies] => Array
        (
            [0] => WP_Http_Cookie Object
                (
                    [name] => rur
                    [value] => PRN
                    [expires] => 
                    [path] => /
                    [domain] => instagram.com
                )

            [1] => WP_Http_Cookie Object
                (
                    [name] => csrftoken
                    [value] => rBgHQnY0L2gWEUiCS2XBMEub0V8b7jz6
                    [expires] => 1553126157
                    [path] => /
                    [domain] => instagram.com
                )

            [2] => WP_Http_Cookie Object
                (
                    [name] => mid
                    [value] => WrLxDAAEAAFMegV-pjax-HlqsUhc
                    [expires] => 2152396557
                    [path] => /
                    [domain] => instagram.com
                )

        )

    [filename] => 
    [http_response] => WP_HTTP_Requests_Response Object
        (
            [response:protected] => Requests_Response Object
                (
                    [body] => <!DOCTYPE html>
<html lang="en" class="no-js not-logged-in ">
    <head><meta charset="utf-8">
        <meta http-equiv="X-UA-Compatible" content="IE=edge">

        <title>
                  Page Not Found &bull; Instagram
                </title>

Same again here so I'll skip ahead...


	<h2>Error</h2>

        <p>Please wait a few minutes before you try again.</p>

.. more skipped error page HTML / JS / CSS ..


       
    </body>
</html>
                    [raw] => HTTP/1.1 429 -
Content-Type: text/html; charset=utf-8
Cache-Control: private, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sat, 01 Jan 2000 00:00:00 GMT
Vary: Cookie, Accept-Language
Content-Language: en
Date: Wed, 21 Mar 2018 23:55:57 GMT
Set-Cookie: rur=PRN; Path=/
Set-Cookie: csrftoken=rBgHQnY0L2gWEUiCS2XBMEub0V8b7jz6; expires=Wed, 20-Mar-2019 23:55:57 GMT; Max-Age=31449600; Path=/; Secure
Set-Cookie: mid=WrLxDAAEAAFMegV-pjax-HlqsUhc; expires=Tue, 16-Mar-2038 23:55:57 GMT; Max-Age=630720000; Path=/
Connection: close
Content-Length: 21390

<!DOCTYPE html>
<html lang="en" class="no-js not-logged-in ">
    <head><meta charset="utf-8">
        <meta http-equiv="X-UA-Compatible" content="IE=edge">

        <title>
                  Page Not Found &bull; Instagram
                </title>

... skipped HTML ...

Fun right?

BUT - here's the thing... once I'd done that and then removed the print_r again, it all worked. Almost as if it somehow flushed it through. Which of course is rubbish. So I tried the same again on each of the other sites that had the problem. Added the print_r, got a page full of Instagram "please wait a few minutes and try again" errors, removed the print_r again and everything is back working. Did this on 4 sites in all, and it fixed all of them.

Make any sense to you?

Cheers, Ian

Forum: Plugins
In reply to: [WP Instagram Widget] Feed show Photos Vertically Not Horizontally | PLEASE HELP ME!

iangeek

(@iangeek)

6 years, 12 months ago

You need to add some custom CSS to your site (e.g through the customiser or Jetpack)

Try this:

.instagram-pics li {
    display: inline-block;
    vertical-align: top;
    width: 16.6%;
}

@media ( max-width: 480px ) {
  .instagram-pics li {
    display: inline-block;
    vertical-align: top;
    width: 49.5%;
    padding: 0!important;
    margin-bottom: -6px !important;
 }
}

Forum: Plugins
In reply to: [All in One SEO – Powerful SEO Plugin to Boost SEO Rankings & Increase Traffic] Auto-generated Description + Keywords not working

Thread Starter iangeek

(@iangeek)

7 years, 8 months ago

Hi Michael,

Advanced Settings are exactly as above (first two boxes only ticked).

The issue seems to be only on posts that have an image as the first item, before any text content. If I remove that and re-publish, the description works again. And continues to work if I then re-insert the image.

Note that it still doesn’t work if I just republish the post without first removing the image.

The client runs Imagify in the background, so I wonder if its some sort of hook from this getting in the way.

Forum: Plugins
In reply to: [All in One SEO – Powerful SEO Plugin to Boost SEO Rankings & Increase Traffic] Auto-generated Description + Keywords not working

Thread Starter iangeek

(@iangeek)

7 years, 8 months ago

Hi Michael,

Just standard vanilla post content / excerpt… No shortcodes or anything like that.

Manually added Description shows fine.

If description left blank it used to auto-generate, but now its not pushing anything through to the head content. Just wondered if this was anything you’d come across before.

I guess its most likely a conflict with another plugin somewhere, but can’t spot anything. Will try setting WP_DEBUG going and see if its flagging anything up anywhere.

Forum: Fixing WordPress
In reply to: Upgrade to 4.7.2 breaks jquery in Menu admin page

Thread Starter iangeek

(@iangeek)

8 years, 1 month ago

Yep, done all the standard things. Still no dice. It was fine on earlier version. Will try to roll back and see if the problem persists.

Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Changing image size for Testimonials output

Thread Starter iangeek

(@iangeek)

8 years, 3 months ago

Thanks Jeremy – I figured you probably would have left it with a filter. You usually do ??

Forum: Plugins
In reply to: [Fluid Video Embeds] FVE Vimeo Embeds

iangeek

(@iangeek)

8 years, 10 months ago

Just had the exact same problem crop up myself… “Division by zero” warning relating to the ‘aspect’ video_meta.

Have Vimeo changed something with their JSON return?

Viewing 15 replies - 1 through 15 (of 33 total)

1 2 3 →