Marks1973
Forum Replies Created
-
Hello everyone,
my hosting provider kinda solved the issue adding the following line:
Header always set Content-Security-Policy "upgrade-insecure-requests;"
in subfolder’s .htaccess (outside BEGIN/END WordPress of course).So, just to summarize the things to check (most of them are obvious):
- You should specify your subfolder in root’s index.php require statement
require __DIR__ . '/(your_subfolder)/wp-blog-header.php'; - Root’s .htaccess should be left as it is when WP creates it.
- Subfolder’s index.php should not have the
/(your_subfolder)part in its require statement. - Subfolder’s .htaccess should contain the line I mentioned at the beginning.
- In WP Settings > General you should state your subfolder’s name in WP’s URL and not state it in website’s URL (as you normally would with a subfolder installation).
For those interested in delving into the .htaccess statement, here’s MDN link.
Cheers!
The latest message from my hosting dates a couple of days ago. It must be quite an effort 🙂
@mmxxi forcing SSL had not resolved for me neither; my hosting has just asked me to grant them administrator access to wp both in the root and in the subdir, to “further address the issue”. I will not waste time to explain them that I have just one installation, but so be it, I’ll do what they ask and get back if anything new comes out.
- This reply was modified 4 years, 4 months ago by Marks1973. Reason: * resolve -> resolved
@mmxxi exactly; @pftsoi as I wrote before I have no plugin at all installed, it’s a pristine installation; so while I agree that wp being in a subfolder shouldn’t change anything, since in my case it does it’s -at least- a starting point for trying and figure the issue out.
If I had to guess I’d say it’s something related to the SSL certificate installed by my hosting, but they haven’t replied yet to my query so… let’s hope and wait (for those who are in my very same situation).@mmxxi that’s a really good question 🙂
I’m about to ask my hosting about it, will let you know.Ok I just deleted everything and reinstalled wp from scratch, this time not in a subfolder but in the root.
No more blank screen on 2022 theme’s edit: all is working now.So what’s that? An ssl propagation issue? (I don’t know if I’m using the right terms but I hope the question is clear).
@mmxxi same problem here. Completely new installation of wp 5.9 in a subdir with twenty-twentytwo theme, no plugin at all. The problem is caused by
/{subdir}/wp-admin/site-editor.phprequesting/{subdir}/?_wp-find-template=trueover http.
Trying various workarounds, will update you if I get anything.Thanks @pdclark , will check on that!
Forum: Plugins
In reply to: [WP Extended Search] Not finding custom post type (with ACF)Hi Sumit,
thanks for your reply; the thing is… my theme is written completely from scratch (and it’s maybe my first complete theme), so since your plugin works as expected with a standard theme (such as twenty-nineteen) I must think that the problem is within my theme, even though I still don’t know in which part (either the template files, or functions.php, or the plugin into which I’ve put my CPT).
So I don’t wish to bother you further until I know better what to ask 🙂
Thanks again,
MarcoForum: Plugins
In reply to: [Event Organiser] Error Message [eo_fullcalendar]Well…
now it’s got back to work…
in a first moment it didn’t show any event… then it didn’t show a recurring yearly event on january 6th 2014 (but it did for 2015 and the following), so I tought I had mistyped the event’s infos (I didn’t).
But now I just got back on the page and there it is, my epiphany event in 2014…
The calendar never stopped appearing, and it did not stuck loading (as it did before I put wp_footer in the footer).
It just didn’t show any event (while ‘eo_calendar’ did).
I don’t know what to say (if not that I can assure you I’m not mad : )))
sorry for bothering and thanks for the quick answer.Forum: Plugins
In reply to: [Event Organiser] Error Message [eo_fullcalendar]Hi again Stephen,
something (apparently) weird just happened: myeo_fullcalendardoesn’t show events anymore. Yesterday evening ok, this morning ko.
– I have wp_footer registered in the footer;
– I have the link to google’s jquery in the header, last version;
– I have switched to 2013 theme… same issue;
– I juggled with permissions… same issue (anyway I didn’t change those things since yesterday evening when it was working).Any other hint?
ThanksForum: Plugins
In reply to: [Event Organiser] Long term repeating events – not listing on eo_fullcalendarHi Stephen,
I was looking right for that: indefinitely recurring events (typical example: a national holiday).
It would certainly be a really useful add-on for the next release.
Bye!Forum: Plugins
In reply to: [Event Organiser] Error Message [eo_fullcalendar]Hi again, just to thank you again and say that everything’s ok (I missed the call to wp_footer in the footer, as your link clearly states).
Best calendar plugin so far.Forum: Plugins
In reply to: [Event Organiser] Error Message [eo_fullcalendar]Hi Stephen,
sorry I should have read that before posting here.
I will bother again just in case I can’t fix the issue.
Thanks again!Forum: Plugins
In reply to: [Event Organiser] Error Message [eo_fullcalendar]Hi Stephen,
1st of all thanks for providing me with THE plugin I needed, no more nor less. I, though, have an issue too with [eo_fullcalendar], that’s to say it simply doesn’t show at all, page or post, no matters.Both the widget and [eo_calendar] works, but I really need [eo_fullcalendar]: I don’t get any error message, simply it doesn’t show anything if the shortcode is the only content in the page/post, or shows a “Loading…” text if there’s any other content.
The main fact is: in another theme, wp’s twenty thirteen, [eo_fullcalendar] works like charm. So we know I would find the problem in my theme (which is really basic), but I really don’t know where to start looking for it. Which are the basic things that need to work/exist in the theme in order to make the [eo_fullcalendar] shortcode work properly?
Thanks again.
Marks - You should specify your subfolder in root’s index.php require statement