sfrangos

I really do not understand the other colleagues here who have a problem with the terms in their agreement?

It seems pretty clear that they are not seeking any ownership of our content, but instead seeking to protect THEIR OWN intellectual property.

Read this link: https://beacon.by/assets/docs/TOU_General_Website.pdf

Did someone find a section that suggests otherwise? As I now understand it, “perpetual and irrevocable licensing terms” do not apply to our content at all.

Hello all –

Jan — I found the posts above ALL relevant to what we are testing.

We too saw the error and ran through the same testing that Adrian K. (thanks for reporting a couple of times on progress, Adrian) describes at top of thread. We manage and support about 25 different WordPress sites — about 10 on Genesis, 14 on Elegant Themes, and 1 on Thematic.

All of those themes are are working out fine — except for just one on Genesis that exhibits the same problem — and resolution (when Permalinks are changed to “plain”).

For other sites checked:

• custom permalinks (usually /%category%/%postname% )
• Under SETTINGS:READING — we have checked and two other sites are fine with a static homepage set
• Check PHP version at host: 5.4. Changing now to 5.6.
• ModSecurity status: not active (we usually turn this off and them use WordFence)

Will report.

Hello All –

Turns out there was a setting in ManageWP (great service) that was on and causing this conflict. That’s why all the other troubleshooting was in vain.

Hope this helps some of you.

– Scott

Hi – we are having the same problem at one of our client sites and it is an installation using WPML — a translation platform plugin. We found a post that describes the problem here: https://wpml.org/forums/topic/insert-media-no-items-found/

Do you have WPML on your site? This could be the problem.

Hail Mr. Dorland –

Any downside you can think of? Right now, the lack of a basic response from the YOast team, when they got where they are by using the free open source plugin marketplace afforded by the WordPress team, is very frustrating. I may just do it as you are doing it.

Cheers –
Scott
#YoastCommunicationFail

@shamrokoz – you cannot insert it in Yoast’s Analytics plugin, hence all of this on the thread wondering about an update.

@mickey Kay — the Yoast comment you posted (thanks) — https://www.hostgarou.com/blog/wordpress/google-analytics-wordpress-support-universal-analytics/ — is dated, so I checked a couple of other places for us:

1) NO REPORT on plans for this at the official WP repository (no roadmap): https://www.ads-software.com/plugins/google-analytics-for-wordpress/

2) NO ROADMAP/COMMENTS at his official site for the plugin: https://yoast.com/wordpress/plugins/google-analytics/

Why? I get it that it is expensive and impossible to answer every support request for free — but why no publishing of an approximate roadmap date for this very key functionality? Why do we have to hunt for an obscure website to get any word from Yoast? Sure, handling free support is not a great option (been there, done that), but on the other hand, Yoast owes most of his success to the free venue AND forum here at www.ads-software.com, right?

Like others, I have my eye on the competition — if the competing plugins are good, they should easily and efficiently be able to outdo the Yoast team on good communication practices. Still waiting for Yoast to update us here so we don’t all have to take to Social Media with the lamentations… ie. #YoastCommunicationFail

Thanks Richard — good suggestion.

FYI… over at the developer’s site, I was referred to a thread about how upgrading the PHP version fixed the error. I did so, and it resolved my issue as well.

See: https://usabilitydynamics.com/products/wp-property/forum/topic/upgrade-to-v-1-41-0-creates-fatal-error-within-wordpress-3-9

Hi Scott –

Good to hear from you here. I would have posted at https://thematictheme.com/ — but they’ve put up a wall and though I’ve requested admittance twice in the last month… no go.

We are using the newest version of thematic. The culprit turned out to be a plugin, one we went through the process of elimination.

Let’s keep in contact. Email me at Webdirexion and let me know what you’ve been up to.

– Scott

Hello Colleagues –

To summarize the problem, we are discussing how use of some caching plugins renders a body class reflecting the last browser captured by the cache… not the true last browser, if I am correct. That would indeed make it difficult to perform browser based style delivery.

@andy – We recently had a conflict with a security plugin that over wrote the .htaccess code, so when you looked at bfgl.com, we were not using page caching. I have just now put it back in play so have a look in a bit.

I am thinking now that by the nature of caching we will still have a problem with intermittent (depends on the time setting for the cache) problems with capturing the browser class in the body tag. I believe this is the only class that should be in jeopardy.

– Scott

Hi –
We have about 40 sites built on the thematic framework, and not one broke, though there are some key deprecated items that we need to remedy.

I think the difference between sites that broke and those that didn’t will often come down to filtering problems in functions.php. Keep a careful eye on how you “enqueue” scripts too. I suggest the following steps to help you fix this:

1. PDF of what’s new, organized by sections showing what was changed, deprecated, and new features – https://thematicmondo.com/thematic-theme-framework-update-new-home/
2. Ask about your problems directly in the new forums here: https://thematictheme.com/forums/forum/thematic-child-themes/custom-child-themes/
3. Work with the Thematic framework concept and philosophy — not against it. This means using the style library in CSS, and not using functions.php hacks to go around the system. You can hook into Thematic, work with its placement of menus in the “access” div and build out any design. Here is another guide to help you: https://thematicmondo.com/wp-content/guides/ThematicMondoGuide-1.pdf

Cheers –
Scott

We have a guide for you listing all the changes for the newly released Thematic 1.0.1 (05.30.12), here: https://thematicmondo.com/thematic-theme-framework-update-new-home/

Such great work by all the developers and community… a big thanks!

Hi –

This thread was marked resolved… but I do not see a resolution?

Please advise.

Scott

Hi –

Same problem here, but was able to log into the admin. area on our installation. I turned off your SEO plugin and problem disappeared. Back on and we get the redirect loop for the public pages — this is on a multi-site set-up and the same problem happened for all blogs. We are running the latest version of WP. We reverted back to HeadSpace2 SEO plugin and there are no problems running it. We love your SEO plugin, however and so look forward to reinstalling after this issue is resolved.

Thanks –
Scott

Hi Nicolas –

We develop using Thematic quite a lot, so I am interested in seeing if I can help you get to the bottom of this. It may be the specific “flavor” of the caching plugin you are using. We use W3 Total Cache, and I don’t think the same problem results. Learn about this plugin here: https://www.w3-edge.com/wordpress-plugins/w3-total-cache/

But if that is the same plugin you use (there are others with similar names), then take a look at one of our client’s sites where we have it in use: https://bfgl.com

If I look at page source for that site, I see:
<body class="wordpress blogid-1 y2011 m12 d31 h22 home singular slug-home page pageid-159 page-author-webfadds page-comments-closed page-pings-closed page-template page-template-NoTitlepage-php mac firefox ff1">

Is this what you did not like? It is actually a very powerful way to take control of what displays on different pages, templates, and even in different browsers. Since each browser gets a class assignment, you could show a different background to people using different browsers, for example, using CSS.

This is not due to W3 Total Cache… these classes are available even without it.

Cheers –
Scott
https://WebFadds.com

Hi –

We develop with Thematic almost exclusively. I can tell you that if you use CSS to place your background in body, or #main, we don’t see these problems.

• Take a look at our site, WebFadds.com
• At that site, the background is in the #main div in CSS, like this: `#main {
  clear: both;
  padding: 15px 0 9px;
  width: 950px;
  background: #fff url(images/sidebarbkgnd.png) no-repeat right top;
  }`

For some tutorials, guides, and videos about Thematic, see: ThematicMondo.com Resources

Cheers –
Scott