Zahak

Hi Barry!

According to WordPress information about the plugin, it should be compatible with php 5.2.4 or higher. But it now requires 7+ (Mm or was it 5.6? Got unsure of other comment, but at least not 5.2 ?? ).

Regards,
Zahak

• This reply was modified 6 years ago by Zahak.

Ehm, but the code states that the version is 2.2.1, while zip file was named 2.2.2. Yeah, confusing…

Sorry, really got too much on my hands.

What I want to achive is that all domains on our multisite should use SSL when logging in. So the issue was that when logged in with other domain than actual main site (first blog/site) pictures etc get https in their url’s. Thus they don’t work for normal visitors, which only use http.

Adding force ssl admin to wp-config:
define('FORCE_SSL_ADMIN', true);

Then I didnt have rewrite rules at the beginning, but tried that too, according to wordpress “Administration over ssl”: https://codex.www.ads-software.com/Administration_Over_SSL

May have forgotten something here, but I think that was it.

It is a bug within WordPress, or close enough…

When entering a 4 digit number, WordPress thinks that you want to show an archive for the year of that number. In you case that would be 2014. As you don’t have any posts published for 2014 yet, you get a 404 error.

When creating a page, you can’t enter 2014 as permalink, it will automatically correct to 2014-2 or something. However it doesn’t do the same thing for posts… (probably as default permalink structure isn’t only https://domain/permalink).

I’m very aware of that memory consumption is not increased due to higher memory limit. But again, the limit is there for a reason.

So I don’t agree with there being no downside, however I can understand that it is nice to avoid those quite unecessary bug reports. Still think it’s wrong solution though.

Anyway, have a nice weekend, and keep up the good work with the plugin.

Hi there Peter,

I know about WordPress constant, and I think that is a totally different matter, of several reasons.

1. WordPress need about 40MB to run. Without that amount, the probability is that it will crash all time.

2. As it is a constant, the developer may easily alter this, but the webmaster (with no real knowledge about php) may not.

3. It is actually nice to be able to increase memory size in admin (using WP_MAX_MEMORY_LIMIT) without touch memory size for default web.

But it is also a bit different, as WordPress is the entire application, responsible for the entire application to work. I still don’t understand why All in one SEO, which is for SEO, would like to alter memory limit. What is next, will All in one SEO alter the wysiwyg? I think that it is very different areas.

The main issue in the end is that the very group that don’t know what PHP memory limit is, can alter memory limit. So what happens if we increase memory limit to 256MB, and there are 20 people visiting our website? Suddenly we use (potential) 256*20 = 5 120 MB. But we only had 4GB memory for starters… so our server, not the application, crash.

Memory limit itself is a guard, to ensure that the application crash, not the server. I don’t think that it is wise to give tools to disable this guard to people who don’t know what it is, how it may affect them, or how it should be set up.

—

It is very simple to deactivate that part of plugin, which I’m very happy for. But as it is enabled by default, and for instance my fellow developers at our company didn’t notice that the performance-part was added at all…

—

A bit curious though, it sounds like it’s quite common that memory limit is set so low, that it breaks the site when activating All in one SEO? Hm, All in one SEO can’t increase the memory consumption that much, can it?

Oh, I’m really sorry. Forgot that I created this thread.

The problem was that someone put a button to switch between desktop and mobile version, without using built in function. This resulted in a simple url, when the built in function would created a javascript creating the cookie.

This would probably not affect anything in a normal environment, but as we use Varnish in front as a reversed proxy, it didn’t work out at all.

So for us it was just to replace button with built in function, and everything worked.

Actually that is pretty much same issue, and putting 2 and 2 together probably results in that the method of cache (memcache vs disk cache) doesn’t really matter. That should be quite important, and is at least good for us to know (since we haven’t heard anything from developer or whatever).

Is this something that mobile-pack-crew is planning to solve?

Was testing out the plugin. Went for lunch, when I came back the settings page had changed from a fan page to Disabled. Now I can’t change it…

Same issue here. Though it managed to post directly to timeline on fb page. But, that only worked for a while, then posting to fb page suddenly changed to disabled.

Suggestion, why not use moderate_comments instead of manage_options? It feels quite natural that whoever has access to moderate comments should be able to moderate a chat as well?

We are thinking of using Quick Chat on a couple of heavy sites, but actually have to modify this since only developers has admin access.

So far a decent plugin, but this feature is vital which actually makes all difference in the world. Also going to be interesting to see how well it perform when going live.

Okey, never mind I guess.. Just finished a fix by myself, which I actually think is prettier.

https://pastebin.com/6KqTviVN

Instead of calling my function inside theme like before, I used add_action to replace parts of wp query.

The problem was that WordPress only calculated on posts connected to category, and not posts connected to tag. As I wanted both, this didn’t work.

As this solves pretty much everything very smooth, I would like to recommend this, instead of manupilating queries in theme. It’s also easy to adjust limits etc with actions/filters.

A couple of more reasons to run one installation:

+ Opcode cache

+ Configuration of web server
(well, that depends on other things as well, but to put it simple we could just push all traffic directly to wordpress if we use only one installation, while we have to use config to divide traffic if we have multiple installations).

Just thought that it would be a good idea to update with some things that we’ve been thinking of ??