lmstearn

Just a quickie – the Front\Static page for the site doesn’t show Disqus content at all, yet the Moderate Disqus Comments is there. The page is set at the Default Template, Disqus docs say it works with Blogs – would that ever be a problem. In which case, the “Alternative Blog” for Twenty Twenty Three has a post date, post title but no body, which doesn’t sound right. Definitely does not work.

Or does Disqus want the actual page slug referenced in the setup instructions?

Also followed this article:

https://bloggingwizard.com/disqus-missing-comments-troubleshooting-guide/

There are hacks in this old thread:

https://stackoverflow.com/questions/5602140/how-to-display-disqus-on-home-page

Worth pursuing, or perhaps the universal code has a trick?

Thanks again.

Thanks for the timely response. ??

@Alvaro Gómez: How nice to come in with helpful comments.

Many thanks. Your first post provides valuable insight to the workings of all this, the second – omg – makes it look all so easy now. ??

And not only that, the Page Summary section has a templates section where which any template can be applied, or even edited, – have to take care any template modifications are sitewide, though.

Was also considering the possibility of adding something like the venerable Disqus, so the commenting user had a choice of logging in through that – probably a question for another thread, (and another time ). ??

Created a static “Home” page, so looking at getting the Single template in for it. Funny thing, it was published today, but can’t find the file (sorting by date) for it anywhere in the ftp listings. In fact the other pages created cannot be located – are they in wp-content somewhere?

Using this idea for the Single template, the single.html page has to be copied with an ID or slug – not sure if there is one created for the above-mentioned “Home” page. To what location must the copied php/html file go?

Thanks again.

Hi Kathyrn,

Thank you very much for looking in, apologies for the delay, did browse through the links, thanks, it’s very detailed and well put together. ??

Although there’s evidence in the following that some key points in the presentations have been missed altogether. ??

Seems like a while ago now, there was, for some reason or issue of post content display, an idea to use an excerpt, followed by comments on the main page. An Advanced Excerpt plugin was used, and it seemed to have provided some visual improvement with some tweakage.

Couldn’t work out all the rationale for using excerpts in any case, might have been something to do with line breaks, in which case from the answer given, was not sure where in what file to place the wpautop code.

Anyhow, the main goal for the site main page is for it to consist of exactly one post, or a welcome message, with comment boxes following for visitor comments, as was the fashion with erstwhile guest books. Pretty much like how it is with the “Single Theme” template, for example. This will work, as you suggested, by replacing the Post Excerpt with Post Content.

Placed a MySite_Comment_Block literal in the link rel of the “Click Here” button, hoping to match it up with a matching reference in the Post Content block, is that how it works?

If, for some reason, the Post Content display doesn’t suit, is it possible to have a static Quoted block with a blank Post Content instead? The effect is the visitors are responding to the Quoted block instead.

As a matter of interest, in order to implement an entire Post Content block in the query loop, One could copy a single template group from the templates page, how to paste/replace it as a group into the main site page?

Thanks.

Here’s what there is in the editor (for 6.1.1):

Somehow, the Post Content block has gone AWOL. Might have inadvertently removed the comment box previously in the editor error. Is there some way to get it back in there with the editor, or is it broken.

Edit: Found the Comment Template by watching this video:

Missed the handy looking WP button at the top left. Will post back on progress (or lack of). ??

Thanks, was lucky to avoid re-installing by logging off both sites, and removing cookies for both, before again logging into oldsite to get

https://mysite/oldsite/wp-content/plugins/wp-phpmyadmin-extension/

Did come across a plugin which claimed to manage separate WP installs in the one session- (missed it second time around)- perhaps it had some kind of basic cookie management to workaround theabove issue.

• This reply was modified 1 year, 11 months ago by lmstearn.

All working, after a chat with the hosting agent, where he kindly populated the empty DB.
An extra complication encountered was that the directory names are all lower case, so https://MySite.com/OldSite/wp-login.php fails whereas https://MySite.com/oldsite/wp-login.php gets in. ??

@bcworkz: Thanks for the info, appreciated.
A question for you or @gappiah.
Copied the files & directories to OldSite, according to instructions, and also this.
Having no direct access to the sql DB file, went ahead and created a new sql DB in the hosting admin panel.
Presumably this DB is pretty much empty on creation, but as it took a little while to initialise in the hosting admin panel, it’s likely to contain the same fields as the original.
In the DB creation, there is a weird length limit on the DB_USER string, where the first nine characters (call them prefix_ids) in the DB_USER name cannot be changed from the original. The length of my user_id (similar to the one on this site) suffix exceeds the max 16 characters allowed in the DB_USER name, so shortened it to accommodate. This may be a problem.
The more pressing issue is not being able to get in at https://MySite.com/OldSite/wp-login.php? at all, a bit like this. The browser shows a “Page Not found” with the same theme as the base site, perhaps because the sql DB in OldSite still points to the base site?
In which case, request the hosting agents to search and update the relevant urls in the new DB?
Thanks again,
Laurie

• This reply was modified 1 year, 11 months ago by lmstearn. Reason: Added more info

@bcworkz:
Fair enough, consider Mysite.OldSite (or equivalent) as having moved on!
Thanks for the info on moving WordPress, having two copies of WP might have a small performance hit, sounds like it is easier and less problematic than a WP multisite sub-directory install, no?
In that case, the article describes very well how to move the site, It seems though, for to have two copies of WP, there is an article somewhere giving instructions to copy it to another directory location.
Never fear, the beginning of the article does explain it:

If database and URL remain the same, you can move by just copying your files and database.

Fantastic, if that is all that’s required, will give it a whirl, and report back.
Thanks.

Hi @george:
Perhaps pasting the question at StackExchange here is easier for reference:

==========================================================================
With reference to the (2010) answer to the MultiSite WP install question, there’s the statement:

“You cannot choose Sub-directory Install in the following cases: If your existing WordPress installation has been set up for more than a month, due to issues with existing permalinks. (This problem will be fixed in a future version.)”

Some years have elapsed since the answer was posted, are we close to the future version yet?

Over here, the option never came up in the first attempt of multisite WP installation. So, at this moment the default choice given is a Sub-domain installation that comes with the caveat of the prohibitive cost of a wildcard sub-domain. Not a desirable outcome, when all that is required here is one subdirectory overriding the main site SSL cert with the following code in the .htaccess file:

RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

Is there a way of prepping a WP Subdirectory install so the existing WP is not completely erased? Perhaps resetting some of the DB items through an admin plugin like WP phpMyAdmin is the way to go, but not sure exactly how to proceed.”

=======================================================================

Right now, according to the above installation guide, the conditions of sub-directory or sub-domain installations have not been met. Question is, can they, with minimal cost and effort?
With the sub-directory option, wiping WordPress is an option, however there are no permalinks yet, and the plugins have to be re-installed and reconfigured. Can we perform some wizardry with phpadmin to allow the subdirectory option to pop up instead?

Yes, this certainly looks as if it can be solved without re-configuring WordPress.
I wish to retain a functional copy of the old (http 90s style) homepage site linked from the WordPress homepage. Created an OldSite sub-directory for that purpose so links to MySite/OldSite worked well.
The problem comes in on the occasion of installing an SSL cert on the site, https fails the linked urls in MySite/OldSite/index.html, along with any other file urls, in a browser.
As to what constitutes resolution, yep, it’s flip this, or tweak that, or ditch the other, to no avail- could it even be the SSL cert itself is causing “unwanted” side-effects? The desired outcome is for the http redirect to only occur in the OldSite sub-directory.
Thanks for your interest by the way.

• This reply was modified 1 year, 11 months ago by lmstearn.
• This reply was modified 1 year, 11 months ago by lmstearn. Reason: Added outcome

Hi @benniledl, thanks for responding.
It’s a partly managed hosting arrangement (Odin under Ingram Micro), so a bit limited in functionality. Have created a subdomain, oldsite.mainsite.com, but it only brings up an ERR_CERT_COMMON_NAME_INVALID, as expected.
Would a subdomain IP do? Looking then, for a solution like this for GoDaddy, but might be out of luck.
Thanks.

After someone else logged in to Admin, the update jump-link automagically appeared!
Also, the “Updates” menu item in the Dashboard showed up with a red exclamation mark for a plugin. Being new to wordPress, wasn’t aware of its existence- so not entirely sure if it was there all along.
Apologies!

6.1, not sure if this or something similar was a problem sometime back with the replaced version.

Thanks Roger, it works at the ABSPATH level, (should have checked it before, apologies). It also worked in some subdirectories before Really Simple SSL, no idea why it stopped working after. Will have to chain the htaccess in the subfolders somehow,- studying something like this might help.

• This reply was modified 2 years, 1 month ago by lmstearn.