Plugin Author
Meitar
(@meitar)
Yeah, I would also encourage you to clear any WP Transients still saved in your WP options table. You might have loaded the larger, older, cached copy. Alternatively, try adding use_cache="no" and see if that clears the transient properly for you.
I’m seeing a lot of SQL rows in the wp-options table such as
site_transient_browser_5d9a37c6a96acca914609d0251…
_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5..
_transient_dash_88ae138922fe95674369b1cb3d215a2
Those are ok to delete?
Plugin Author
Meitar
(@meitar)
None of those are this plugin’s but yes, by definition a transient should be temporary cache, and thus should be safe to delete. See the WordPress Transients API.
1) Deleted expired transients.
2) Reinstalled plugin
3) Looked at wp-options table and find only one entry for igdv, that being gdoc_settings.
Still getting the fatal memory error.
If you believe transients might still be a problem, I’ll back up the (local) site and delete all the transients.
I appreciate the guidance on this. I’m assuming that updating to WP 4.8 is unlikely to do anything but possibly crash my site d/t plugins not being updated yet.
Plugin Author
Meitar
(@meitar)
No, I was not suspicious of the transients per se, but the notion that perhaps your memory exhaustion was the result of a cached too-large spreadsheet. I can’t right now but when I can I will have a peek at the spreadsheet itself and see if I can reproduce the issue on my end given your shortcode.
PPS would a copy of the callstack be useful to you?
Plugin Author
Meitar
(@meitar)
Well, sure, I guess, but I’ll not pay attention to bits other than my own plugin. I don’t have the time or resources to do so. No one pays me for working on this, as you may know.
Yes, you are doing wonderful things!
I don’t get paid for my work, either. I’m retired and do gratis programming for a few small non-profits and a couple of elderly friends.
Saw this message flash before my eyes when looking at the wp-options again:
“Warning: a form on this Page has more then 1000 fields. On submission, some of the fields might be ignored do to Php max_input_vars configuration.”
I’m not sure that changing the limit will do anything. Did some searching on that message and in one instance, someone mentioned a daemon was already running. So I’ll reboot, restart AMPPS and see if magic happens. It usually doesn’t though, for me. 🙁
Hi Meitar,
OK, I messed around with increasing the memory limit in wp-config. No change. Then I tried a different google spreadsheet:
[gdoc key=”https://docs.google.com/spreadsheets/d/1xgfyJOobS206cXBXszbdoFyykjJYxdCkg5BtbuBGtQw/edit?usp=sharing” http_opts='{}’]
The one above works. This one, with columns swapped around and headers formatted, does not:
[gdoc key=”https://docs.google.com/spreadsheets/d/1oeWv6_L9nPrCNXCgqs8pcJ9Nd4pdDh0QsTzTmrEaxY4/edit?usp=sharing” http_opts='{}’]
Not only that, but the page rendering is screwed up so that when logged in as admin, the WordPress menu bar doesn’t even appear at the page top, although the header & other theme page elements do. Even with WP_DEBUG turned on.
So there’s something rotten in the google spreadsheet. Who would have thought…
I’ll keep flogging away on this and let you know what, if anything, I find.
Profanity, profanity, profanity!!!
Plugin Author
Meitar
(@meitar)
Took a look at your spreadsheet today. You said you deleted rows, but you didn’t. You just cleared their contents. The cells are still there. If you load the sheet in your browser, you’ll see it takes ages to load. So the PHP memory error is no surprise, it is exactly what it sounds like: the sheet is bigger than the PHP memory_limit set on your server. Try actually deleting the empty cells (rows/columns) themselves, not just their contents. Specifically, you have fifty thousand (50,000) rows, and the vast majority of these rows have zero content. They do not need to be in your spreadsheet at all, and probably shouldn’t be.
There is an open enhancement request in the issue tracker for this plugin to more gracefully deal with this situation, but it has not yet been implemented because it’s so unusual for someone to use this plugin in such a way as to load this much data in the first place. I will (eventually) get around to it, but it may still not be for some time (months? Years? Who knows, given this being a one-person volunteer effort and all that).
D’oh! I just figured that out 6 minutes ago when copying from one column to another. The column height was highlighted apparently down to infinity, which I did not pick up previously with these old eyes.
When I think about it, every spreadsheet program I’ve ever seen (starting w/ VisiCalc…) seems to have gazillions of rows & columns by default. Since they all have the ability to add rows & columns, you’d think they’d start with a more modest number, say, 20 x 20, and let folks add more rows & columns as needed.
It’s also odd that copying a column from spreadsheet A to spreadsheet B, where spreadsheet A had only 30 rows, caused B to end up with gazillions of additional blank but apparently not null, cells/rows.
I am so sorry to have wasted your time. And very grateful, that you were so kind as to reply.
Everything coming along now. Found support threads here and helpful things on the DataTables site, was able to twiddle column widths, get vertical scrolling working, disable paging and pretty much the only thing remaining is css.
Thank you again for a wonderful plugin. Will add you to the “Credits” page of our non-profit.
