alxvallejo

Well yes, but for me I would need to track the breakdown of custom taxonomies so I’m thinking I need to use wp_localize_script and pass some PHP variables to the javascript term parameters. I’ll let you know if it works and if you can think of an alternative approach, even better!

Pages still show…

Correct, the styling is not applied

Thanks for the tip! That’s great except that the output is not quite as pretty as the in-line CSS I applied to the tables on my site.

Why in-line CSS? I’m converting tables from Microsoft Word via Live Writer and due to variability and complexity of tables on my site, this is the best way to export the tables in HTML while keeping the formatting in tact.

As an example, here is just a sample of the output with the first table row of html below. The classes of the table don’t mean anything since they’re tied to MS Word but the background colors and fonts are what need to be preserved. The first row should have a background color of #0099cc (blue) but the output is like this:

https://screencast.com/t/mrkHygBAD2

From this point, my goal is get print-friendly versions of my table with CSS formatting preserved. Your help is much appreciated but it looks like I’ll need to write my own CSS print-friendly version.

I see this error a lot also. The page order is not always in tact when I see the results.

Would you mind explaining how the plugin screwed your database?

How are you installing it? I’ve found that there are 3 directories that need permissions to be modified (or monitored): 1) data/solr << This is where I place my schema and solr.war install 2) /etc/tomcat6 3) /var/log/tomcat6

Make sure those have proper permissions established

“crisp and clean way”
Can you be specific?

What page results in the error? Also, how are you hosting the Solr instance: on your own server? through a third-party?

I also noticed that the plugin was caching my front page, meaning that there was a HUGE security flaw because the cache was taking my admin account and caching the login. Users were unable to navigate but the front page was exposed.

me too, I hate to see this thread unresolved.

Just to add to this conversation, I received the following error:

Warning: require(TAR.php) [function.require]: failed to open stream: No such file or directory in C:\xampp\htdocs\dell\XCloner.php on line 40

Fatal error: require() [function.require]: Failed opening required ‘TAR.php’ (include_path=’.;\xampp\php\PEAR’) in C:\xampp\htdocs\mywpfolder\XCloner.php on line 40

The .tar file is in the folder though so I’m not sure what I’m doing wrong.

Way too much of this
https://screencast.com/t/j8q3CuRh

Ah, nevermind, I found the icon that integrates with uploads on a post. I spoke too soon.

It works on 3.2