BBIndikator

Yes..!

It was a mistake by myself and Frank guided me the right way. Thank you for this!

Best regards

I’ve sent a email to your gmail-address..

I don’t think that this is the reason, cause I use AO on other websites with renamed wp-content without any problems, too. Here is an example.

Awesome, thank you : )

If you mean the origin-settings inside MaxCDN, I looked for this as first step before I wrote to you. The origin inside MaxCDN is setup properly to https://domain.de.

But it seems that you linked me to the right way. I purged the complete cache inside the CDN-settings. After this I cleared the page-cache one more time (this time I erased the complete folder over ftp) and I cleared also the browser cache.

It seems that purging really everything solved the problem.. Now Pingdom and GTMetrix love our website : )

Thank you for this Frank!

Best regards,
Bruno

The other website is on the same server with the same theme

Yes, it’s always the same, no matter what cdn-sub is used. But it happens just with ssl enabled. I asked the support from MaxCDN before. They told me that everything is setup properly..

I have another website with almost the same setup (Zencache and 4 CDN-Subs), but without ssl. Everything works fine there.

Bruno

Hello gVector Team,

sorry for delay, thanks for your answer..

it seems that it happens just under test-purposes. In our case we modified some redirection-rules (this do not create the error).

For testing we sent some first-comments for a user (comments to moderate) to adjust the confirmation-mail.. This error happens, if we moved this first-comment to trash and sent a new first-comment for this user without cleaning the trash before. If we emptying the trash before a new first-comment for this special user, everything seems to work fine..

This is not a normal user-scenario, so I think there’s no need to change anything from your side. If you still need a link to an example URL, let me know. Then I sent it to your support-email.

So I think this topic can mark as resolved.

Thank you and best regards

Hey there, hope you’re well..

Same problem here.

[01-Jul-2015 12:52:30 UTC] PHP Catchable fatal error: Object of class stdClass could not be converted to string in path/to/groups/lib/access/class-groups-post-access.php on line 398

In our special case we use wpDiscuz. If we click the “Load more comments” – Button, we get an error in Chromes Console:

jquery.js?ver=1.11.2:4
POST https://domain.de/wp-admin/admin-ajax.php 500 (Internal Server Error)

And then you find the first message inside the php-error.log.

In our case we need to deactivate Press Permit Core itself to fix the error.

Is this a problem of Groups or of Press Permit ?

Best regards

does your CSS really vary from page to page, or do you have a number of “pagetypes” for which the above-the-fold would be the same (e.g. “typical” blog post, standard page, homepage, …)?

To find this out is the goal : ) We start on various pages with another pagelayout and with different elements at the beginning. And a lot of this “above the fold” elements are heavy customized in special areas inside our custom_stylesheet. And we also work a lot with media-queries..

You’re definitely right. On pagetypes like posts the above-the-fold css will not vary.. But here we need also to include our media-queries..?

although ideally you wouldn’t have different above the fold CSS for each page)

Yes, you’re definitely right with this. I never recognized this above-the-fold theme till yesterday (we use PO, Caching, AO : ), and a lot of optimization on the server (VPS) itself). During reading your faq I realized that it really makes sense to work with it, but I think this means a lot of refacturing our code especially with our responsive design..

you can actually use the API (“autoptimize_filter_css_defer_inline”-filter) to override the inline CSS on a per-URL basis

Thanks you for this tip! I will definitely take care of it. But I think here we also have to find out a way to include our media queries ??

Bruno

P.S. we build up a plattform to help other peoples to reach their personal goals.. In order to your donation rules I hope it’s ok for you to donate to a project in africa from a friend of us..

Yes, that’s a better way to fix it… Everything is fine now..

I reordered some of our css-styles and js-files to work properly with AO. That means that in our case (more than 100 active modules together with Plugin Organizer) no exclusions are needed..

We have to do some tests for special cases, but you’ve done a really amazing work with AO.. Thanks a lot for it !

The only thing that is really hard stuff is the theme “above the fold”, cause it’s various on our website from page to page.. I think it makes more sense in this case to work with a server-side solution.. We tried googles mod_pagespeed, but it seems to work not very well (PageSpeed Insights itself do not recognize that it is turned on and on GTMetrix and Pingdoms you will be downgraded and pageload itself rises up)

We will see : )

Thank you and best regards,
Bruno

Good morning Frank,

thanks for your answers. I will digg into your FAQ and the linked blogs there to get it to work properly (now I know that I have to do that : ) )

With out of the box I meant, that it do not break the page, what is a really good starting point. We use a lot of extensions and plugs (together with plugin organizer), so the rest seems to get fixed with some modifications from page to page (or slug to slug).

But it seems to be worth to go deeper with your plugin.. It makes a solid job.

Wish you a nice sunday, too.

Thank you and best regards
Bruno

Hey @ projectmunton,

this time it isn’t a feature inside PO, cause it is till this version designed to make important improvements just for the Frontend.

But Jeff plans to add some addition functions in a future release to optimize the backend, too.

The only thing you can do this time to improve the backend, is to create a filter for

https://your-domain.com/wp-admin/

After creating this filter you can deactivate plugins in your backend (after setup all settings) that not been used on the backend itself or post-types, cause every new post-type creates a new permalink and if you deactivate a plugin on /wp-admin/, the plugin will also deactivated on a new post-type cause it is a child of /wp-admin/. Exactly that’s the reason why it so hard to optimize backend, cause as you can see in your own backend: it’s not possible to use “pretty” permalinks, but PO works just with permalinks inside the backend this time.

Normally it is not a problem to deactivate a plugin inside backend after set it up, cause on frontend the plugin will get it’s settings from the database, but if you do it on this way, test it.

If you have some really hardweighted plugs for the backend you can proof to deactivate them on your filter /wp-admin/ too. Then you can create a new entry on a post-type where this plugin normally is used. After this done you can generate a new filter for the permalink of this new created post-type-entry, cause the link will stay permanently after creating a new entry and activate your plugin on this filter (you can deactivate a plugin on a parents filter and activate it on a child filter). But that needs some work and it is just worth if you’re plugin is really hardweight..

Resolved.

If someone has the same problem: in our case the participant was also a customer (WooCommerce). But you need the same caps like a subscriber..

Use something like “Capability Manager Enhanced” to solve this..