javipas
Forum Replies Created
-
Forum: Plugins
In reply to: [Ghost] Error message “Site is experiencing technical difficulties”Tried to change some PHP parameters in my WordPress’ VPS (I use EasyEngine there to automate some processes, but I don’t use EE on the Ghost VPS, that’s a different one). According to this support article I’ve changed this on the “custom.ini” file:
max_input_vars = 1234
max_memory_limit = 256M
max_execution_time = 300
upload_max_filesize =100M
post_max_size =100MAfter restarting nginx and PHP the plugin still doesn’t work. Same error, even when I try to download the .json file.
I’ve installed that new version and the problems have dissapeared: my homepage loads quickly, its size is what I’d expect (around 500KB) and there is no episode download in the background that made page size and load times really bad.
I will be testing the behaviour in the next few days, but it seems the problem is solved. Congrats, Craig 🙂
I’d like to start also by saying that SPP is really great, thank you so much for your work on this plugin. It makes podcasting from WordPress quick and easy.
Having said that, the same happens for me: with the HTML5 player effectively downloads the episodes on each homepage load, I’ve got Seriously Simple Stats installed and after a couple of refreshes my 10 items homepage make that stats increment by that number. With the normal player that doesn’t happen.
In fact, an anaylis on pingdom shows pagesize at over 120MB (uauh!) and I can only think the podcast episodes are actually being downloaded on each homepage refresh. Here are a couple of images showing that analysis from my podcast site.
Thanks!
Forum: Plugins
In reply to: [Front-end Editor for WordPress] 0.10 doesn't work on WP 4.0Hi Janneke, in fact I’ve got the blog in a system composed by Nginx+PageSpeed, HHVM, MariaDB and, finally, WP 4.0.
One of the Github project followers pointed me that and linked to the new version that already works in this version. Fantastic new interface, I’ve already mentioned that in my blog on a post dedicated to the plugin (in Spanish, I’m affraid). Thanks again for a great job, greetings!
Forum: Plugins
In reply to: [Front-end Editor for WordPress] 0.10 doesn't work on WP 4.0Sorry Janneke, did you have the chance to take a look at the problem I mentioned before?
Regards!
Forum: Plugins
In reply to: [Front-end Editor for WordPress] 0.10 doesn't work on WP 4.0The same exact problem I’ve got, cars111. Let’s hope Janneke can tell us if there is some way to solve that…
Forum: Plugins
In reply to: [Front-end Editor for WordPress] 0.10 doesn't work on WP 4.0Janneke, could you give some hint about the error message that WP showed when trying to activate the plugin? I still haven’t updated to WP 4.0 because of this 🙁
Forum: Plugins
In reply to: [Front-end Editor for WordPress] 0.10 doesn't work on WP 4.0I can’t activate the plugin, there’s a syntax error I can’t detect :/ even by looking that line and that kind of error. Everything seems fine to me 🙁
Parse error: syntax error, unexpected ‘[‘ in /home/javipas/domains/xxxxxxx.com/public_html/wp-content/plugins/wp-front-end-editor/class-fee.php on line 111
Forum: Plugins
In reply to: [Front-end Editor for WordPress] 0.10 doesn't work on WP 4.0Not here 🙁 I’ll try to update everything tonight, thanks for the update Janneke!
Forum: Plugins
In reply to: [Front-end Editor for WordPress] 0.10 doesn't work on WP 4.0Fantastic!
Forum: Plugins
In reply to: [Redirection] 403 Forbidden on some redirectionsAdamstar1, I’m the sysadmin, no webhost involved. The site is on a Linode VPS with Debian 6 (Nginx, PHP-FPM, MySQL) I manage.
Sorry, forgot to mark this as solved.
I’ve finally solved the issue. And it was a really stupid change. When asked to add the typical lines:
define(‘WP_ALLOW_MULTISITE’, true);
define(‘MULTISITE’, true);
define(‘SUBDOMAIN_INSTALL’, true);
$base = ‘/’;
define(‘DOMAIN_CURRENT_SITE’, ‘example.com’);
define(‘PATH_CURRENT_SITE’, ‘/’);
define(‘SITE_ID_CURRENT_SITE’, 1);
define(‘BLOG_ID_CURRENT_SITE’, 1);I was doing it BELOW the “/* That’s all, stop editing! Happy blogging. */”.
And all I had to do is to insert those lines ABOVE (over) that line. It works now, and it was not a Nginx issue, just a tiny change on the wp-config.php file.
Uauh.
I’ve tried your suggestion and used the file from http://rtcamp.com/tutorials/nginx-wordpress-multisite-subdomains-domain-mapping/
This is the /etc/nginx/sites-available/mysite.com config file:
map $http_host $blogid {
default -999;#Must Read - http://rtcamp.com/tutorials/nginx-maps-wordpress-multisite-static-files-handling/
#foo.example.com 3;
#bar.example.com 4;
}
server {
#@DM - uncomment following line for domain mapping or you will need to add every mapped-domain to server_name$
listen 80;
server_name mysite.com *.mysite.com ;
#@DM - uncomment following line for domain mapping
#server_name_in_redirect off;access_log /home/myuser/domains/mysite.com/logs/mysite.access.log;
error_log /home/myuser/domains/mysite.com/logs/mysite.error.log debug;root /home/myuser/domains/mysite.com/public_html;
index index.php;location / {
try_files $uri $uri/ /index.php?$args ;
}location ~ \.php$ {
try_files $uri /index.php;
include fastcgi_params;
fastcgi_pass unix:/var/run/php5-fpm-myuser.sock;
#fastcgi_pass unix:/var/run/php5-fpm.sock;
#@DM - uncomment following line for wordpress-plugins that uses value of _SERVER["SERVER_NAME"] e.g.
#fastcgi_param SERVER_NAME $http_host;
}#WPMU Files
location ~ ^/files/(.*)$ {
try_files /wp-content/blogs.dir/$blogid/$uri /wp-includes/ms-files.php?file=$1 ;
access_log off; log_not_found off; expires max;
}#WPMU x-sendfile to avoid php readfile()
location ^~ /blogs.dir {
internal;
alias /home/myuser/domains/mysite.com/public_html/wp-content/blogs.dir;
access_log off; log_not_found off; expires max;
}location ~* ^.+\.(ogg|ogv|svg|svgz|eot|otf|woff|mp4|ttf|rss|atom|jpg|jpeg|gif|png|ico|zip|tgz|gz|rar|bz2|doc|$
access_log off; log_not_found off; expires max;
}location = /favicon.php { access_log off; log_not_found off; }
location = /robots.txt { access_log off; log_not_found off; }
location ~ /\. { deny all; access_log off; log_not_found off; }
}No luck though. nd I don’t access the network-setup: when I logout and login again the system goes straight to that page. I haven’t got the normal WP multisite menu to manage sites, it keeps showing me the network setup, and just that. But always with the message “Warning: An existing WordPress network was detected” 🙁
Forum: Fixing WordPress
In reply to: HTTP Error on image uploadIf you’re based on Nginx, there’s a parameter called client_max_body_size on the /etc/nginx/nginx.conf that you should change.
As mentioned here the solution should be this if you want, for example, uploads up to 20 megabytes:
http {
include mime.types;
default_type application/octet-stream;
sendfile on;
keepalive_timeout 65;server {
client_max_body_size 20M;
listen 80;
server_name localhost;# Main location
location / {
proxy_pass http://127.0.0.1:8000/;
}
}
}