trident60
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: New Page takes 90 seconds to loadYup – deactivated every plugin, tried a few default themes…didn’t fix it.
It seems there was a WordPress Core ticket opened some time ago, regarding this, #28219 – but it was closed after someone determined it was a plugin. Then it was opened again under # 32264 – and was just assigned 11 days ago – so hopefully they will realize it’s not plugin related (I’ve never used either of the plugins referenced in the original ticket) and a fix will be out soon ??
Forum: Fixing WordPress
In reply to: New Page takes 90 seconds to loadGood thinking Bet – just tried it, no change. I even tried that file
from previous versions of WP – and even going back to 3.5 ?? – everything
functioned exactly the same way ??Seems to be querying for “video” and “audio” media…and going through my
post_meta table – which is large – but I don’t use any video or audio – yet, so
I wish I could just turn it off.Thank you again!
Forum: Fixing WordPress
In reply to: New Page takes 90 seconds to loadHello Bet,
Thank you for the suggestion!I had optimized the DB but it didn’t make a difference.
Also, I upgrade to WordPress 4.3 Alpha and the same query now takes 162 seconds…lol
I know, it’s only the Alpha version, but I was hopeful this issue may have been resolved.
Thank you again for your time.
Rob
Yes, very. I do have Solr and WPSolr running on my production site – but the only facets that work are “tags” – and that is the current WPSolr and Solr 5.0.
Healthitlink.com
healthit1.cloudapp.net is the test site – FYI.
It completed.
Now, when I do a search, I get no results!
Don’t you love giving away stuff? LOL
It’s actually indexing MUCH faster than the other versions…at 3000 already….80K more to go. I’ll give you the update when it’s complete.
Okay – I emptied the index and it now shows all the docs to be indexed….so I will do that now – that’s going to take some time.
Thanks!
For some reason it wasn’t working in Safari…but I tried it on Chrome, on the Mac, and here are the debug results:
******** DEBUG ACTIVATED - Beginning of new loop (batch size) ******* ******** DEBUG ACTIVATED - Query documents from last post date ******* Query: SELECT ID, post_modified, post_parent, post_type FROM wp_posts WHERE post_modified > %s AND ( post_status='publish' AND ( post_type='post' ) ) ORDER BY post_modified ASC LIMIT 100 Last post date: 2015-06-11 22:59:28 ******** DEBUG ACTIVATED - No more documents, end of document loop *******
I’m on a mac….Safari, Firefox, Chrome…I have a Windows server….let me log into that and try.
And that would prevent it from seeing anything to be indexed? Because when this was working it showed documents in the index – but clicking “Empty the Solr Index” didn’t have an impact.
Is there a way to fix that?
Updated to 3.5, clicked the operations tab, checked “Display debug infos…”, ran the index – there was no information displayed. What you see below is exactly what I saw.
If you tell me where/how to get the sql query you need I’ll be glad to get it.
Solr Operations A total of 0 documents are currently in your index 0 document(s) remain to be indexed The indexing is incremental: only documents updated after the last operation are sent to the index. So, the first operation will index all documents, by batches of 100 documents. If a timeout occurs, you just have to click on the button again: the process will restart from where it stopped. If you need to reindex all again, delete the index first. Number of documents sent in Solr as a single commit. You can change this number to control indexing's performance. Display debug infos during indexing
Not sure exactly where to get that information…I posted lines 612-632. Is it different lines you need? Is what you need in the actual class-wp-solr.php file?
global $wpdb; // Last post date set in previous call. We begin with posts published after. $lastPostDate = wp_Solr::get_hosting_option( 'solr_last_post_date_indexed', '1000-01-01 00:00:00' ); $tbl = $wpdb->prefix . 'posts'; $where = ''; $client = $this->client; $updateQuery = $client->createUpdate(); // Get body of attachment $solarium_extract_query = $client->createExtract(); $solr_indexing_options = get_option( 'wdm_solr_form_data' ); $post_types = $solr_indexing_options['p_types']; $exclude_id = $solr_indexing_options['exclude_ids']; $ex_ids = array(); $ex_ids = explode( ',', $exclude_id ); $posts = explode( ',', $post_types );
Yes – I’ve been doing that all along. There is no difference, no errors showing, with version 3.4. I click “empty the Solr index” and the page just reloads and still show the same:
A total of 0 documents are currently in your index
0 document(s) remain to be indexed