kalico
Forum Replies Created
-
Forum: Themes and Templates
In reply to: [Colibri WP] Colibri borked defaults in Hillstar ThemeI did some more digging and figured it out. Hopefully this will help someone else.
- Found a page called “Blog” (with slug “blog”) and deleted it.
- Found a page called “Front Page” (with slug “hillstar”) and deleted it.
- Under Settings >> Reading changed it back to “home page shows most recent posts”
All I can say right now is that it really would have been nice to know what was going to happen when I activated Colibri.
Forum: Plugins
In reply to: [User Post Gallery - UPG] Login PagePS I am looking at Flexi now. I appreciate the suggestion, it looks great. Will it be replacing UPG?
Forum: Plugins
In reply to: [User Post Gallery - UPG] Login PageThank you. I figured out the problem I was having and I’ll share it here in case it helps someone else.
When I was first testing this plugin, I had selected a login page in the settings. I later moved that page to the trash.
The plugin continued to use that page URL when I set login=true, so it was showing a “Login Please !” link when the user was logged out, and that link was to a non-existent page.
The settings screen at this point showed “None” as the selection in the dropdown.
What I had to do was restore the trashed page, publish it…then the plugin found the page again and put it up in the dropdown.
At that point, I was able to select “None” and save the settings, and with that, the “Login Please !” link was changed to plain text.
It might be useful to have a check for “if exists” on the login page, and if not, then clear out the field in the database so that the link really is “None”.
It would also be really nice if, in the case of no login page being selected, the plugin would default to the wp-login.php page for the site’s domain (or have a URL field for an alternate login URL).
HTH
Thank you! I hope it will be considered for a future upgrade.
OK, I think we’re getting closer! 🙂 But what I want is for OTHER users to be notified when someone else’s image is activated, i.e., when the image is owned/posted by someone else. Not notifying the user who posted the image, but notifying other people who are in the same contest and want to see the other images in the competition.
Thanks for your quick replies! 🙂
Thanks @contest-gallery but actually I was hoping to inform end users, not the admin. I want the people who are participating to know about new entries so they can see them. Like if the BCC selection could include an email to “all subscribers” or something like that. Of course, they’d have to be able to opt out too, I guess.
- This reply was modified 5 years, 1 month ago by kalico.
Forum: Reviews
In reply to: [All-in-One WP Migration and Backup] Multisite Support $199I was going to make the same complaint: non-commercial use should be allowed. But I do understand what @yaniiliev is saying. A multisite network is WAY different structurally than a stand-alone site. Unfortunately, I still won’t pay $199 for personal use. I’ll just have to do it the hard way.
Forum: Themes and Templates
In reply to: [Twenty Twenty] Background image screws up text visibilityThanks @macmanx
I have never been a fan of background images on an entire post and that was not my intent. I can now see that I was confused by the Twenty Twenty theme customization options, where the only image option turned out to fill the entire background of all posts and pages. Definitely not what I was going for 🙂
I’ve done a bit more with this now based on your feedback and I’m understanding the theme behavior better.
I removed the background image — which, incidentally, was not an easy task. That section of the theme customizer had no option to remove….in fact it looked as if I had never selected a bg image at all. I ended up going through the process again to add a different image as the background, and then I saw the option to remove it.
I then went to the sample page and gave it a featured image (for the Cover template), and now THAT image is used for the parallax effect without it also being the background image to the whole page. Much better.
My last question (for this round anyway)…
You mentioned a header image…where would I find the controls for that – in the theme or in Gutenberg blocks? And are we talking about a header for the entire site, or on a per-page basis (the former presumably being part of the theme, and the latter, being in Gutenberg)?
I know how to do that sort of thing old school, but that’s not the purpose of this exercise. 😉
Forum: Networking WordPress
In reply to: Domain MappingI never had any luck getting around the default behavior after the domain mapping plugin failed. I still have the situation where all admins need to login at the mapped site’s admin page, which sets off our security trap and they are stuck. My workaround was to use the WPMUDEV “Cloner” plugin (which is legacy, but available as open source – https://github.com/wpmudev/cloner … and of course they may be other options out there) to clone the one site that uses a mapped domain. Now, when anyone needs to edit the mapped domain site, I temporarily point the domain at the clone. This allows us to access the otherwise-blocked site via primarydomain.com/slug/wp-admin and every so often, I re-clone the site to keep it up to date.
It’s a hassle. And not a good solution at all if you have multiple sites in your network with mapped domains that you need to edit on a regular basis. But for me, it happens to work well enough…for now.
Forum: Plugins
In reply to: [WP Photo Album Plus] Directories not createdThat seems to have done it! Even the photos I originally uploaded are working – you must be regenerating those on the fly. Very nice!
The log indicated a particular folder structure that was missing, so I have created it.
https://share.getcloudapp.com/z8uwxvgN
Thanks for the great and fast support!
Forum: Networking WordPress
In reply to: Multisite forcing login for every siteOne other comment: to @singer74 — You earlier mentioned that your site is “in a subdirectory”. I wanted to be sure you don’t confuse that with a “subdirectory installation” of WP Multisite.
Putting all of WP into a subdirectory of your webroot is a thing. You could have a non-WP website at example.com, which lives in the webroot on index.html (/path/to/webroot/index.html) AND a WP blog in a subdirectory of the website at example.com/blog — where your entire WP codebase lives in the literal subdirectory /path/to/webroot/blog on the server.
But a WP Multisite has two options for how the URLs are formed for all the sub-sites (a.k.a. “blogs”) within the multisite are fashioned. In a “subdomain installation” the URLs are formatted as subdomains (blog1.example.com, blog2.example.com, etc.). In a “subdirectory installation” the blog URLs are formatted as virtual subdirectories: example.com/blog1, example.com/blog2, etc. They do not literally live in subdirectories on the server named blog1 and blog2.
You could potentially have a WP Multisite running in a subdirectory path of your SERVER, but it could be set up as a “subdomain installation” or a “subdomain multisite”. Not that I recommend such a wild configuration, but I’m just trying to show the difference between them. Subdomain vs subdirectory in multisite is just referring to the configuration of multisite blog URLs NOT the location of files on the server.
If you knew all that, hopefully it will help someone else who stumbles on this 🙂
- This reply was modified 6 years, 9 months ago by kalico.
Forum: Networking WordPress
In reply to: Multisite forcing login for every siteWow! I am so glad you posted this and a big thank you to @bcworkz for explaining what’s going on. I have posted about EXACTLY this issue on my own site several times since June, including a bug report to Trak, and got no solid answers. I knew I was not alone, because there were several reports in mid-June about the exact same issue — but no one could explain the cause. Just broken websites and no answers.
So what happened in the universe? Did all the browsers change their security protocols at the same time? That’s the only thing that makes sense to me, because it was working just fine and then “BOOM”. I did not make any changes to my site, it just broke.
I was using the WPMUDEV domain mapping plugin (which is now legacy but still works) and so far it is the only one that seems to fix the issue of multiple logins, because it has a “cross-domain login” setting.
However, I had that plugin, with that setting on, installed and working PRIOR to the day everything went BOOM, so at the time I thought that was the cause of failure — now I think it is the only solution.
I suspect that there may have been some other plugin that initially reacted badly to whatever happened in the universe (e.g., we had some early symptoms involving WMUDEV’s Defender plugin, which is for security). Then some cascade of events led to a conflict with domain mapping. Or perhaps both problems happened at the same time, and I didn’t realize it.
You might want to give that plugin a try! It’s on github now as open source, but without support (unless you’re a member of WPMUDEV, which I recommend, since they provide support for everything WP). I’m going to try using it again, with the Defender plugin disabled. I have tested it on a sandbox site, and so far it is the only solution to the multi-login problem.
Security question:
Our larger problem is that we long ago bypassed the use of wp-login for greater security. We were getting slammed by bots trying to hack their way into our site via the standard page, so we disabled it and created a custom login page with a different URL. But all the plugin options I have considered to avoid logging in on each subsite (e.g., turning WP into an Oauth client/server) have failed because they rely on the standard wp-login page.
Do you all have any recommendations about using or not using the standard login page? Does everyone have as much trouble with it as we do, or are we doing something wrong? Is there a better option than using a different page?
Forum: Networking WordPress
In reply to: Domain MappingNo, not really. I pretty much came to the conclusion that wp domain mapping requires the superadmin to log in on every subsite by default.
I have been doing extensive testing in a completely fresh install and I cannot get it to behave any differently, so I believe that to be the default behavior — it expects you to log in at least once to set a cookie, then you should be OK after that.
I don’t like that behavior, because it messes with something we have done for security: we disabled access to wp-login (which gets slammed with malicious attacks) and created a different login page. So for my production configuration, this doesn’t work at all. I literally cannot log in as the superadmin to any subsite in the network if it has a mapped domain.
The only “fix” I have found (in my sandbox site) is to use a legacy plugin from WPMUDEV which offers a cross-domain autologin feature. https://github.com/wpmudev/domain-mapping#domain-mapping
This is actually the plugin I was successfully using for several years on production, but in June we had some really massive and sudden failures which — after extensive plugin conflict testing — I could not attribute to anything but the domain mapping plugin. So I disabled it, hoping to just use default domain mapping. But for the reasons stated above, it does not work for us.
As a workaround on my production site, I have set up an additional subsite with the slug /maintenance and marked it to discourage search engines. I made a home page there that says we are doing maintenance. When we need to post something on the mapped domain site, I point the mapped domain at the maintenance site, and put the real site back to its default site URL in Network >> Sites >> Settings (our multisite is configured with subdirectory URLs, so I am changing it to example.com/slug) then we can temporarily access the dashboard via example.com/slug/wp-admin. When we are done, I change the domain mapping back to how it should be.
This is “easy” in the moment, but overall it’s a massive pain in the @$$ and not sustainable.
My next step (tonight, actually) will be to test the domain mapping plugin again on my production site after hours when traffic is slow. I need to find out if I can enable it without bringing the site to its knees again. I’ll post back when I learn more, and if you have any specific questions I didn’t answer please feel free to ask!
Forum: Networking WordPress
In reply to: Multisite subdirectory domain mapping on localhostDid you ever get this worked out @dhyanakendra ? I think the problem here might be a misunderstanding of the “subdirectory” concept. WP multisites that are setup as a “subdirectory” installation (as opposed to a “subdomain” installation) do not have whole entire sites in literal subdirectories with paths as you’ve shown here. The “subdirectory” configuration refers to the way your permalinks are structured, e.g., example.com/site1, example.com/site2, etc. (in a subdomain configuration, your sites would have URLs like this: site1.example.com, site2.example.com)
- This reply was modified 6 years, 10 months ago by kalico.
Forum: Networking WordPress
In reply to: Domain MappingThanks @autotutorial
I think there is some confusion here, because I am not trying to map a domain to /wp-admin/ or map a domain to the primary site or vice versa. I’m just trying to do very STANDARD domain mapping to one of the sub-sites in my network. It should be super simple (and it DOES work on the frontend) but something is affecting how the wp-admin links work. I posted a video below, hopefully that will help.
I did as you suggested and reviewed every one of those in the database. I have not made any changes. You can see screenshots here and leave comments by selecting text or screenshots, if you wish:
I also made a screencast showing what I am trying to describe, because I think that the situation is too confusing for words alone.
Important: the primary domain is dev.nrocnetwork.org (dev.nroc.org is the mapped domain) I have not mapped anything to /wp-admin/
Observations about the database entries:
– some of them are http, some are https – could that be a problem?
– in wp_blogs, both the primary and mapped domain have the path / but the others all have /xxxxx as the path – that might be how it should be, not sure.I have followed all instructions at https://ww.wp.xz.cn/support/article/wordpress-multisite-domain-mapping/
There is nothing mapped to “folders” in my site. I added a screenshot to the doc above (bitly link) showing what my folder structure looks like.
Thanks for all the efforts to help me out!!! 🙂
- This reply was modified 6 years, 11 months ago by kalico.