Xephan

I was trying to solve the same problem with WordPress’s rewrite rule interfering with .htpasswd protected folders. The simplest solution is actually to change WordPress’s rewrite rule

From
RewriteRule . /index.php [L]

To

RewriteRule ./ /index.php [L]

With this, the additional block of rewrite rule doesn’t seem to be needed anymore.

I know it’s kinda late but I faced the same problem and didn’t find any resolution for most of the queries about this error here.

So for propensity’s sake, this could be caused by include/require of a file that has the same name as another within your PHP include search path.

The fix if this is the issue faced is to specify the full path of the actual file to be included instead of just the file name or relative path as is normally done.

The theme is coming up under main, i.e. https://www.cultofangels.net/main/
Do you mean you want the blog to appear under the domain root, i.e. at https://www.cultofangels.net/ instead?

In which case, WordPress will have to over-write your existing site, so you should make a backup first before trying to install again.

Also, you might need to check with your webhost. Their quick-install for WordPress may have been set up to always install WordPress in a directory rather than the domain root.

Or maybe the part where you think it’s asking for your site name is actually asking for the location where you want to install your blog. So leaving it blank might work.

Look at this
https://codex.www.ads-software.com/Installing_WordPress

or this
https://www.ads-software.com/hosting/

or the easiest way, this
https://wordpress.com/?ref=wporg-download

Did you guys delete the sql database before re-installing? If things are still found in the database or wordpress can’t create/modify tables, then it could be a database permissions issue.

I assume you have check that your PHP and SQL versions are up to date?

@lasso: does it make a diff if you shift the location of the define statement further up in wp-config, e.g. near the top after the defines for user/server/password?

@creativelasso: I didn’t let it do the upgrade since I saw a lot of people having problems with that as well. I deleted the 3.1 installation and database, copied in a fresh set of 3.2 files and installed again. And it worked. Totally unexplainable since nothing changed in between.

Before you do anything, backup your database and any customized code/plugins/themes.

I was having similar problems getting multi-site working on a clean install of 3.2, in my case, the network menu never shows up anyway. Deleted it, install 3.1 to check I didn’t miss a step in procedure. Deleted 3.1, installed 3.2 and it just worked. So as useless as this might seem, if nothing else works, try installing 3.1 first ??

Since it doesn’t seem like you’re doing any hacking of the codes, maybe you should be posting in https://jobs.wordpress.net/ instead of here?

It’s probably different because your PHP code was sending the wrong URL via the text widget rather than your actual URL.

Facebook appears to match URL up to a certain point, I’ve tried chopping off characters from an URL and it still shows the correct count.

So the chances are somebody else was trying to do the same thing and therefore generated the extra likes you see for the incorrect gobbleygook.

Depending on how exactly do you want to limit the length, the following functions would work, from the easiest to the most complex

Limit by pure character length, so you may end up with partial words
https://us2.php.net/manual/en/function.substr.php

Limit by words, splitting on space. But this would treat words separated by spaceless punctuation as one.
https://us2.php.net/manual/en/function.explode.php

Limit by words, splitting on non-words, it can mistake certain valid characters as non-word but you can specify additional “word” chars to overcome it

https://us2.php.net/manual/en/function.str-word-count.php

Split using regular expression, not likely needed since in most cases the previous function would do
https://us2.php.net/manual/en/function.preg-split.php

In all cases, you end up with an array of words which you just have to delete excess before imploding it into a string again.

My workaround to that is to use the same domain names on my development setup, then just playing around with two copies of the hosts file by using a script to switch between the two for checking the live site and for working on the dev site.

Admittedly every now and then I forget to switch and things get confused for a moment. But it does make dumping the sql data easier.

This older thread might help ??
https://www.ads-software.com/support/topic/adding-tinymce-editor-for-custom-field-when-editing-post-page?replies=6

Although you’ve solved it with an external mod, I would like to suggest it would probably be easier in the long run to do this simply by using a custom field in the user profile to determine who can/cannot access the files.

Then use a WordPress page to do the checking and sending of the files. This gives you more flexibility in the long run and easier to maintain.

Don’t use plus signs, they have specific meanings in an URL which is why your slug get parsed into two words; + means a space in the query part of an URL.