[@hnla Participant 14 years, 7 months ago]

Install xampp it’s a better AMP package, set up your httpd,conf file for Apache to use vhost containers, use your hosts file to set local domain e.g mysite.dev then you can run as many installs as you like from a directory of your choice along with fully qualified domains albeit locally resolved.

[@hnla Participant 14 years, 7 months ago]

One of these aspects that’s not really buddypress related- it classically sounds like permissions issues as that is what 403 means so not sure why your tech says perms are ok, might be a case that file perms are ok but that the web server hasn’t got correct access (group or owner) to write to files ?

either way it’s going to be something that we will not be able to help with too any great extent, check your server access logs try and track down the issue there, also ask your techie to check that the web server does have correct perms to write to files – can you do stuff like media uploads ok?

[@hnla Participant 14 years, 7 months ago]

Do the pages actually exist? you have to have empty pages created and there to be selected, either named as conventionally or named as you wish.

[@hnla Participant 14 years, 7 months ago]

Commendable! all but adding atahowlerhooper to the list that is

Guess I should have seen that list. My only worry with the list and all that work you’ve put in is that it rests on the forum links and posts themselves remaining true, be nice if there were some easy means of bundling stuff into a template zip or some such ‘thing’.

Right I’ll sidetrack post no more now I’ve vented my fury at atahowlerhooper

[@hnla Participant 14 years, 7 months ago]

You will need to explain exactly what you see them having access to – registration / users are a WP aspect what role a registered user has on your site is dictated by settings in your dashboard under settings > general where you should see a setting to change the default user role the default is set to ‘subscriber’ and allows your users very little power to edit anything in fact nothing, so have you changed something?

[@hnla Participant 14 years, 7 months ago]

No, I would follow mercime’s advise to set up a test install to trial aspects of BP with but also activate BP on main site but until ready keep the main components de-activated except profiles, friends, messaging and use the WP menu to build your main menu so that you can ensure ‘groups’, ‘forums’, and ‘activity stream’ pages aren’t listed, this way you can run with user account/profiles from the front end and slowly introduce the other BP components as and when required.

[@hnla Participant 14 years, 7 months ago]

I know I always mince my words, should really learn to say it how it is

Table layouts are unsustainable, fragile, break all notion of separation of content from style, throw one of the main virtues of CSS-P out with the trash, on many a forum dealing in Standards based frontend coding you’ll find many that will simply not help with table layouts, 10 years down the road and we really should have seen the back of them.

I’m sure Mercim’s changes will be effective, but lets hope we don’t see too many BP themes popping up using it – sorry Mercim not meaning to insult your efforts :p

In fact Mercime you a have helped with so many third party theme conversions to BP that you must have a good working list of themes now? for a codex list ?

[@hnla Participant 14 years, 7 months ago]

> Atahualpa is definitly a very achieved tool for wp users.
> make the two work together, but just can’t quite get there.

Sorry to interject in a rather irritating fashion but I’ve run across this theme before and to be brutally honest you should not waste the time trying to make it compatible with anything it’s a table based layout and as such utterly outmoded and redundant and like a red rag to any long suffering Standards based coders

As for remembering settings you only need to trawl through the options table and others if you are actually wanting a completely clean install of BP and this is seldom really required.

[@hnla Participant 14 years, 7 months ago]

If that’s the link you get that is essentially mal-formed you need to look carefully at what you’ve written.

You should show the actual code you wrote rather than, or, as well as the result.

This should work in a standard page.php file:

`<a href="profile/”>my logged in domain members profile`

[@hnla Participant 14 years, 7 months ago]

please turn off your caps lock before replying further.

What you describe sounds like styling issues, cross browser styling issues. You do not mention anything about you setup, this info helps to determine what might be going on. If you have a child theme/ bp compatible theme running then please disable it and revert to the BP default theme and check whether you still see the problem, also – just in case it’s a plugin issue – de-activate all plugins other than BuddyPress.

[@hnla Participant 14 years, 7 months ago]

You either copy paste the url in full into your post/page editor or if you need that link to be programmatic then you would need to modify your single post /page template file to add a BP style url to logged in user.

Explain exactly what it is that your are trying to do, if adding a hardcoded link directly to a template file then you’ll need something like:

`profile/`

[@hnla Participant 14 years, 7 months ago]

@kosarr please only start one thread per question.

Closing this duplicate – continue in:
https://buddypress.org/community/groups/installing-buddypress/forum/topic/404-the-requested-url-not-found-on-this-server/

[@hnla Participant 14 years, 7 months ago]

I’m guessing that people are not following all the instructions on that page? At the end there is mention of removing the wp-options entries, it’s these that will be re-entering certain values.

[@hnla Participant 14 years, 7 months ago]

Without sight of the theme and it’s code most of would be guessing in the dark, unless we had specific experience of this particular theme.

This support forum is really geared to support for BP and it’s default theme, if this child theme has support that ought to be the first place to ask about customising it, if it doesn’t then you will need to provide a bit more info on the theme and / or a link to your site and someone may help you modify it.

[@hnla Participant 14 years, 7 months ago]

Good stuff, glad it’s sorted – easiest things are often overlooked for something deeper

[@hnla Participant 14 years, 7 months ago]

This won’t help:

id=’Shoot Up-css’

ID’s are unique thus not only can you not have the same name repeated on a page you can’t have two tokens on the same ID.

That you have and the second being up-css suggests that you left a space in the directory name for your theme – close it up, no spaces allowed. Spaces in paths / file names are a truly evil thing and only Windows lets it happen, in Unix it aint allowed.

[@hnla Participant 14 years, 7 months ago]

Insufficient detail in order to be able to help you really, sounds more like a WP issue though?

[@hnla Participant 14 years, 7 months ago]

It should log you out in the standard WP fashion to the wp-login page.

[@hnla Participant 14 years, 7 months ago]

Think you meant: issie_userwuser_loggy_innie()

[@hnla Participant 14 years, 7 months ago]

Did you follow the point I made in the other thread? It seems to be an issue with caching plugins – don’t use them unless you understand how they work and you really have need of them don’t install them just cos you like the sound of them.

You will need to work out whether your caching is the root cause by running a few tests such as deleting extra users, re-enabling caching and attempting to replicate the error at will, then you should be fairly certain what plugin causes the issue.

[@hnla Participant 14 years, 7 months ago]

PJ we still don’t know what files you found to be an issue, Paul has applied a patch/fix for an issue where avatar paths are hardcoded to ‘http’ – as I suggested might be the issue or one of the issues – knowing exactly what files you had issue with would still help to confirm this is actually the problem.

If the baseurl is correctly set to ‘https’ then ‘http’ isn’t an issue, it’s only an issue at present as the secured page attempts to retrieve objects from a non secured protocol ‘http’

Paul’s links to a ticket where he’s added a patch for the avatar issue this – when included – would normally appear in the next release (1.6) could be ported back to 1.5 branch?, but you may need to add the workaround to your files for the moment.

Have you a link to this site? Is it possible for us to see the mixed content in action?

[@hnla Participant 14 years, 7 months ago]

PJ you do need to try and identify what files are the issue, Paul did ask that first time around, that info would allow both of us to have a clearer idea of what to look at.

Images paths are often the culprit in this sort of mixed resource scenario, which is why I mentioned them.

On a sidenote although it may seem an odd idea to run an entire site under https, there are those that advocate ALL sites changing to https regardless of whether they have obvious need for it such as payment gateway security.

[@hnla Participant 14 years, 7 months ago]

Likely image urls are the culprit as is often the case with ssl connections. A certain amount of googling will fill you in on the ins and outs of using SSL and the warnings that are generated (it’s not broken SSL it’s just a warning that the page request has mixed resources)

Possibly BP needs to be doing some checks to see how the server is configured with respect to SSL, not something I have had cause to look at with BP.

[@hnla Participant 14 years, 7 months ago]

Folks it’s very bad forum nettiquette to post in existing threads with ones own issues as things rapidly become confusing trying to respond to multiple questions in that same thread – even if original question ‘appears’ closely relate to ones own.

You need to create a new topics please.

Have you read and followed the advice / instructions in this thread?

Disabled all plugins? All the same instruction applies please follow those before posting so we know if those aspects have been ruled out.

When you have done that and issue continues please create a new thread and mention first that you have disabled all plugins and reverted to default theme to test and issue persists.

Also if you are running any caching plugins please disable those first before any other tests and see if that clears things up.

Closing this thread as it’s run it’s course.

[@hnla Participant 14 years, 7 months ago]

And are permalinks working? You have to have them set to something other than the default i.e you cant have /?p=1234

It sounds as though your permalinks are not working so you may need to investigate that, establish that your .htaccess file can be writen to by the server.

I would have a read through of the WP Codex guide on permalinks:

https://codex.wordpress.org/Using_Permalinks