Not a lot of informations to go on here including some that does not make any sense.

How does simple Press include ‘a bad version of jQuery’??? The only version we ever load, if and when we load one, is the version that ships with WP. How does he consider that’ bad’???

And we certainly try to only load it when needed. If he knows of somewhere this is happening when it’s not needed we would certainly look into it. But if thesis chokes when the wp version of jQuery is loaded, that is something thesis would need to worry about and fix.

So more details please….

I’m not a programmer, so I don’t know if I can be of much more help.

I can tell you that there is definitely a conflict. I’ve tested Thesis 2.0 and the current version of Simple:Press on my main site and on a new test site. The test site only has S:P, Akismet, and WordPress Importer plugins installed and activated. Simply activating the basic S:P plugin blocks the Thesis admin menus, before the full S:P plugin is even installed. After full installation of S:P, I tried every possible combination of integration and display settings under the Integration menu. Nothing resolved the conflict and unblocked the Thesis menus. Deactivating the S:P plugin instantly resolves the conflict, however.

Comparing page source of the main Thesis admin page with and without S:P activated (I can provide you with the full page source of both if needed), some differences I see are:

In the head:

<link rel='stylesheet' id='spMenuStyle-css' href='http://test.prometheus-unbound.org/wp-content/plugins/simple-press/admin/resources/css/spa-menu.css?ver=3.4.2' type='text/css' media='all' />
<script type='text/javascript' src='http://test.prometheus-unbound.org/wp-content/themes/thesis/lib/js/menu.js?ver=3.4.2'></script>
<script type='text/javascript' src='http://test.prometheus-unbound.org/wp-includes/js/jquery/jquery.js?ver=1.7.2'></script>
<script type='text/javascript' src='http://test.prometheus-unbound.org/wp-admin/js/utils.js?ver=3.4.2'></script>

The S:P stylesheet and jquery.js?ver=1.7.2 are loaded only when the S:P plugin is activated.

In/after the footer, this is without S:P activated:

<script type='text/javascript'>
/* <![CDATA[ */
var commonL10n = {"warnDelete":"You are about to permanently delete the selected items.n 'Cancel' to stop, 'OK' to delete."};/* ]]> */
</script>
<script type='text/javascript' src='http://test.prometheus-unbound.org/wp-admin/load-scripts.php?c=1&load=admin-bar,hoverIntent,common,jquery-color&ver=3.4.2'></script>

And this is with S:P activated:

<script type='text/javascript' src='http://test.prometheus-unbound.org/wp-includes/js/admin-bar.js?ver=3.4.2'></script>
<script type='text/javascript' src='http://test.prometheus-unbound.org/wp-includes/js/problem-with-post-edit-buttonoverIntent.js?ver=r6'></script>
<script type='text/javascript'>
/* <![CDATA[ */
var commonL10n = {"warnDelete":"You are about to permanently delete the selected items.n 'Cancel' to stop, 'OK' to delete."};
/* ]]> */
</script>
<script type='text/javascript' src='http://test.prometheus-unbound.org/wp-admin/js/common.js?ver=3.4.2'></script>
<script type='text/javascript' src='http://test.prometheus-unbound.org/wp-includes/js/jquery/jquery.color.js?ver=2.0-4561m'></script>

I hope this helps.

Sounded like someone gave you info and it sounded incorrect unless they consider the jQuery that ships with WP to be bad. So was hoping for more info along those lines and what research they did.

Is thesis free? That is, something we could download to research…

Mr Papa said
Sounded like someone gave you info and it sounded incorrect unless they consider the jQuery that ships with WP to be bad. So was hoping for more info along those lines and what research they did.

Not sure. You might contact Chris for more information. I guess the conflict came up in testing. He also recommended talking to @byobwebsite for more details.

Is thesis free? That is, something we could download to research…

Afraid not. I can’t speak for Chris, but maybe he would be willing to let you look at the code for the purpose of resolving the conflict?

Sorry, Andy and I are both on road and can’t see the code via email. So will be couple days before I can look at. Maybe Brandon can see take a look.

Hard to really research too with actually running thesis.

In your comparison, did you have any simple Press plugins active? Is so, might be interesting to see without any.

And stil troubled by thesis having issues with wp jQuery loaded. Mighty strange that it wouldn’t like it. Hopefully it’s not loading a non wp jQuery version.

But agree if it’s sp loading jQuery and we are not on forum admin page, we should not be forcing it to load. Hence my question about no sp plugins. Wonder if a plugin us doing it. Will certainly research that.

Mr Papa said
In your comparison, did you have any simple Press plugins active? Is so, might be interesting to see without any.

But agree if it’s sp loading jQuery and we are not on forum admin page, we should not be forcing it to load. Hence my question about no sp plugins. Wonder if a plugin us doing it. Will certainly research that.

No S:P plugins installed or active in that comparison. It’s just the core S:P plugin on the test site.

Okay, thanks. Will look into when back to computer later this week.

Hi

Mr Papa said
Okay, thanks. Will look into when back to computer later this week.

 I fixed this issues

go to wp-content/plugins/simple-press/sp-config.php

find this line

define('CONCATENATE_SCRIPTS', false);

and set to true like this

define('CONCATENATE_SCRIPTS', true);

nice, I guess…    doesnt really make any sense…  requiring a concatenation of admin scripts is counter intuitive… but glad it works!

this was thesis 2 also?

This is the work around for using Thesis 2 with SimplePress; my question is why is the statement false and why do you say it is counter intuitive.. I’m just wondering if it’s a security issue. I’m not code knowledgeable; I did find out it means to string together, but that’s about it.

Thanks!

No, definitely not a security issue… concatenation of scripts just means combining multiple js scripts into a single one… you load only one file vs multiple – so less http requests… if it works, you will get an ever so slight speed increase… but we are talking about the admin here…  and too many times it does not work when concatenating – something breaks which causes problems…  so we disable it for an overall better user experience…

still mystifies me how a wp theme could require concatenation of scripts in order to work…  or not work if not concatenated… if I were to guess, thesis actually has a script enqueueing problem and its trying to access a script that has not been loaded yet (ie header vs footer)… by concatenating them into single file, you do guarantee its available…  but if that is the issue, and dont want to cast stones since I do NOT know, its just covering up an issue…

Thanks  Mr Papa! Didn’t want to open one can of worms to close another.. which could be the case at some point but as long as it’s all working I’m happy

glad to help! you are welcome! we like working too!