Flexer
Forum Replies Created
-
Thank you so much.
I just noticed that, and resolved the issue, and the feed is working.Clifford was not to blame merely a coincidence
Forum: Plugins
In reply to: [Columns] Responsive ColumnsTo make these responsive, you must use media queries.
You can do this by over-riding the default styles as the dev suggests.
“Styles are in columns.css. If you’d like your own margins and stuff, dequeue the columns.css style during wp_enqueue_scripts with a priority of 11 or more.”To just do in your theme it will depend on how your theme does responsiveness in Twentytwelve as an example the “default” styles are for mobile so you add this to your child-theme css above the first media query
.columns-2 .column, .columns-3 .column, .columns-4 .column, .columns-5 .column, .columns-6 .column{
width: 100%;
}
Then for each column size you add back the default width
Below is for two columns.@media screen and (min-width: 600px) {
.columns-2 .column {
width: 47.5%;
}}
Hope this helps.
Nope. It was a new site.
But on the same server I host maybe 12 installs with the approximately same number and type of plugins, and this is the first time for this error. Even upgraded Jetpack on most of them.Thanks
DaveedNo problem; 4 weeks no response from OP, I thought it would be good to revive.
In any case it seems that upping the memory for the account took care of the error. Although 64M should be fine; in this case 96M was required. Just wondering if the memory requirements for Jetpack have changed? Specifically during the authentication process.
Over and out
DaveedHi,
I will try to revive this post as I am running into the same issue:
Wordpress 4.1.1 – some plugins but no caching ones.Install JetPack – no problem
Connect to WordPress.com: Fatal PHP Error;Tried this twice: both times renaming plugins/jetpack resolves the issue. Both time the error is the following:(From cpanel Error Log)
Haven’t noticed the issue in older installs with Jetpack connected; But I will not update Jetpack untill I hear back.
[Tue Feb 24 06:02:23.411084 2015] … PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 30720 bytes) in /public_html/wp-includes/class-IXR.php on line 1056
[Tue Feb 24 05:33:17.088940 2015] … PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 30720 bytes) in /public_html/wp-includes/class-IXR.php on line 331
Thank you
DaveedForum: Plugins
In reply to: [Slideshow Gallery LITE] wp_head and wp_footer errors showing after upgradeJust went live- and the error is gone.
Thanks again for your lovely plugin.Is there a PayPal I can buy you a beer or a fruit juice 🙂
Feel free to email me directly at daveed@flexer.caDaveed
Forum: Plugins
In reply to: [Slideshow Gallery LITE] wp_head and wp_footer errors showing after upgradeNope no caching plugin installed.
> Twentytwelve Child
> Advanced Custom Fields Pro
> Akismet
> Jetpack by WordPress.com (no caching)
> Limit Login Attempts
> Under Construction (site is not live)Could it be as it’s hidden behind a coming soon page?
Going live today- can see then.Thanks
DaveedEDIT: Previous version did not throw this error; and nothing else changed except a new version of Jetpack I believe.
Forum: Plugins
In reply to: [Slideshow Gallery LITE] wp_head and wp_footer errors showing after upgradeYes, this just happened to a client site as well.
Forum: Fixing WordPress
In reply to: WP 3.9: Warning: strpos() expects parameter 1 to be stringCool that worked.
I previously opened a support ticket with JetPack and I’ll update them with your solution turtlepod. It should go into future code so your solution does not get erased when JP gets an update.
Thanks
DaveedForum: Fixing WordPress
In reply to: WP 3.9: Warning: strpos() expects parameter 1 to be stringThe theme was twentytwelve child
It was while embedding the Jetpack form. If you Google the error it looks like it is other Jetpack forms.Flexer
Forum: Fixing WordPress
In reply to: WP 3.9: Warning: strpos() expects parameter 1 to be stringThanks for the fix @webstract Marketing. If you google the error you get tons of sites, must be a 3.9 bug.
Wouldn’t this fix be erased whenever we update wordpress? I was using TwentyTwelve and got this issue. Alterantively perhaps it will be fixed in the next update to 3.9.