gwslink
Forum Replies Created
-
Forum: Plugins
In reply to: [SiteOrigin Widgets Bundle] Update Resizes Widgets Sporadicallyalign-items:center by itself gave me all images stacked on top of each other center of the page. Using align-items:center with the other CSS still displays the image larger than with the previous Widgets version. It seems the only fix is to uncheck the “Bound” box.
I will check for updates this afternoon and see if the updated version behaves properly.Forum: Plugins
In reply to: [SiteOrigin Widgets Bundle] Update Resizes Widgets SporadicallyI tried that and it didn’t help. Since you brought attention to the custom CSS, here is what it looks like. I just added the line that you indicated to it. Does this show the source of my issue?
.widget-mh,.so-widget-sow-image {
min-height:110px;
}
.bottom_aligner {
display: inline-block;
height: 100%;
vertical-align: bottom;
}
.sow-image-container {
position:relative;
min-height:110px;
display: block !important;
}
.so-widget-image {
position:absolute;
top:0;
bottom:0;
left:0;
right:0;
margin:auto;
}Forum: Plugins
In reply to: [SiteOrigin Widgets Bundle] Update Resizes Widgets SporadicallyNot sure exactly why, but the few images that were resized have been corrected by unchecking the “Bound” box. It is still checked for the others.
That’s it, thanks.
I have found something that I didn’t know existed – WP REST API. I have not done a whole lot of research, but it seems that I can use this to update criteria in existing pages. Although this will not completely resolve the need to automatically process a received XML file, it will provide a starting point.
I now have more details. The plan is that the file list will be received in an XML file and the files will be downloaded into WordPress. I like the ability of your gallery to display all of the files in a directory. If I could put the new files into their own model directories and then automate the scan for new files in each directory, that would serve part of the automation desires.
Thanks. I will give it a shot.
Forum: Fixing WordPress
In reply to: Making Dev Site On NginxNGINX version is 1.10.0 running on Ubuntu 16.04
Not sure why it works, but it definitely does. I am documenting the settings so that I can copy live to dev since it has changed over the few days that it took to get the dev site up and running. Thanks for the help.Forum: Fixing WordPress
In reply to: Making Dev Site On NginxMore research revealed the need for RELOCATE to be added to wp-config. Now, when I access the site by IP and port number, it retains the correct site address. After I changed the Site Address, it is working. I had apparently made another change because it is changing back with a refresh. Progress is good, though.
Forum: Fixing WordPress
In reply to: Making Dev Site On NginxMy reason for thinking that it is a WP config setting is that I type in
http://gwcompare_dev.gradywhite.com
and it changes to
http://gwcompare.gradywhite.com/wp-login.php?redirect_to=http%3A%2F%2Fgwcompare.gradywhite.com
If I take off the redirect and change to _dev, it logs in and then still redirects to the main site. I believe that I may have just talked myself into the correct solution, though. I have the “My Private Site” plugin installed and it, of course, was duplicated into the _dev copy. I am going to disable all plugins at the database level and see if I can access the _dev site. Do you have any experience with that plugin?Forum: Fixing WordPress
In reply to: Making Dev Site On NginxOops. I have both the server name and root set. One of the posts that I came across said to use the IP in listen, so I did that also. I was also looking at fastcgi as the culprit, but unable to find a solution there. I have this same file in both sites-enabled and sites-available. I have also removed default. Do you see anything funky that I may have missed? Any other suggestions?
The only differences between that file and the “dev-less” file are a listen set only to 80 and the removal of “_dev” in all applicable lines.
server {
listen 192.168.20.5:88;
server_name gwcompare_dev.gradywhite.com http://www.gwcompare_dev.gradywhite.com;root /var/www/gwcompare_dev/public;
index index.php;access_log /var/www/gwcompare_dev/logs/access.log;
error_log /var/www/gwcompare_dev/logs/error.log;location / {
try_files $uri $uri/ /index.php?$args;
}location ~ \.php$ {
include snippets/fastcgi-php.conf;
fastcgi_pass unix:/run/php/php7.0-fpm.sock;
}
}Forum: Fixing WordPress
In reply to: Making Dev Site On NginxI forgot to mention that. The separate config is in place but I believe that the root directive was left off. Thanks, I didn’t want to commit a server just for that purpose.