[@hnla Participant 16 years, 3 months ago]

I only ever seem to get this issue on one server that I manage through Plesk or at least have the option of, other servers I administer via SSH never give me this issue, leading me to think something in the way Plesk deals with groups isn’t the best.

[@hnla Participant 16 years, 3 months ago]

It’s one of or a combination of two issues: the folder permissions may not be set correctly (these can normally be corrected via a decent FTP client folders generally need 755 and files 644)

Check the WordPress codex for the correct permissions required

The other issue and more likely the problem here is that the server group hasn’t got the correct permissions to create and write to directories, if you are on shared hosting you may need to contact your host to get this sorted out and also ensure that PHP ‘Safe Mode’ is turned off.

[@hnla Participant 16 years, 3 months ago]

@r-a-y
@hnla – Just for sanity’s sake, I tried again. This time via “Super Admin > Blogs”. I clicked “Edit”, then added an existing user to the sub-blog that way. Works. Can you check to see your wp_bp_user_blogs table to see if it’s recording anything?

May be testing at cross purposes here? Also I t may well be my misunderstanding of things.

It isn’t so much sub blogs issue it’s a general member of the main site BP / WP blog has no means of easily logging in to the dashboard to make a post as a ‘contributor’ or a level elevated from ‘subscriber’ (As was raised by the OP on this thread?) further to that I realised that also there was a similar issue when installing WP as single blog in that users – at any level – had no bp-adminbar links to access the dashboard (normally under ‘My-blogs’) this issue is known but I had to quickly whip up a crude function to test user level and drop a series of dashboard links on to the adminbar if !bp_core_is_multisite() not ideal but functional.

The issue which still puzzles me is that on, for example, a multisite install, no user blogs created; if I take a user and elevate their role to ‘contributor’ or even ‘admin’ they still get no means of logging in to the dashboard, not at least under the my-blogs link (as the super admin gets) Perhaps they were never intended to be able but it does mean an awkward route for them to be able to make a post, in my mind I expected them to receive a link to the main blog under ‘my-blogs’ as the super admin or main admin gets, but it isn’t their blog so they don’t.

I would suppose that a bit of a rewrite of the ‘my-blogs’ function would solve things for both missing link on single installs and for elevated member roles to receive the link as well, I was starting to look at ‘my-blogs’ and adapting it but time is my enemy at the moment.

[@hnla Participant 16 years, 3 months ago]

Good stuff, Windows is an issue re mod_rewrite and .htaccess but isapi_rewrite does work well but you have to pay a license fee or use the lite version

[@hnla Participant 16 years, 3 months ago]

Yes the problems were multiple and as I described earlier Glad it’s working now, just take extra care when chopping templates around and with what I suspect is a mixture of theme files?

[@hnla Participant 16 years, 3 months ago]

Oh and lastly the sidebar is not being called into the correct position, again compare the two pages, in index.php ‘sidebar’ is called just before #content closes and in single.php you are calling it after #container closes and the comment after #container states

You just need to be careful when moving page elements around in templates and check carefully that they are in the correct position as on other pages.

So decide what sidebar you need to call if it is that left-sidebar then you will need to give it the same rules as the #sidebar, add the #sidebar-left id to the #sidebar ruleset in default.css. however this is simply a unnecessary extra div around an #sidebar so I would lose it altogether then you shouldn’t need to adjust the CSS, much better though is to call the same sidebar as the index.php (the locate_template call) and lastly you need to ensure that the sidebar is called into the same position before #content closes.

[@hnla Participant 16 years, 3 months ago]

Compare the two pages index and single post, you are not calling the same sidebars; in single.php you appear to be calling ‘left-sidebar.php’ and this does not have the same rules applied to it as does ‘sidebar.php, and would need to if it were to function in the same manner as on the index page.

Not sure where you got ‘left-sidebar.php’ as it doesn’t appear as part of the bp-default files.

[@hnla Participant 16 years, 3 months ago]

Hardcode something in the sidebar just to be sure it ought to be displaying something or not simply hidden due to not having widgets.

[@hnla Participant 16 years, 3 months ago]

explained in last comment.

Look at that code, specifically look at the classes and the id’s on various elements such as the sidebar where the value needs to be quoted it needs to be plain quote marks as your keyboard will enter. At the moment the quote marks are not correct character entities they are angled .

Check the code you posted to pastebin, I have edited the first quote mark of the class on the element ‘content’ to show you a visual comparison of the two different marks – compare to the sidebar element at bottom of page:

http://pastebin.com/gqYuJU4i

I don’t claim this is definitely going to cure the issue but it is a problem for correctly behaving browsers and needs to be put right before moving on to look at other possible causes – if the isue still persists

[@hnla Participant 16 years, 3 months ago]

Firstly It’s better if people didn’t piggyback (hijack / resurrect) old threads, it appears to make sense when one finds a thread that mirrors ones own issue but is not generally considered best practice.

Secondly scroll back up to mercims post and the link to the sort of detail you might need to provide the community in order that accurate help may be offered.

To the issue it strikes me that you haven’t possibly? completed all steps to enable MS (Multi Sites) if the answer to that is ‘Not sure’ then likely you haven’t and it may be wise to read through the steps outlined in the WP codex:
https://codex.wordpress.org/Create_A_Network

I notice that your site is running as a sub domain this will likely be an issue if trying to run blogs as sub domains.

You might want to check that you have and can write to the .htaccess file (can you change the permalink structure from the backend and have it report success or a message that it can’t update the file)

[@hnla Participant 16 years, 3 months ago]

It is a known issue and a patch has been committed and should be part of the 1.2.6 release, that will hopefully drop very soon.

[@hnla Participant 16 years, 3 months ago]

Look at your IDs and classes, backspace out the existing quote marks and replace using your keyboard characters ” ” what you have at the moment is incorrect and due somewhere to copy and pasting characters outside the permitted character set, the sort of horror that Word places in markup if not careful

[@hnla Participant 16 years, 3 months ago]

Not sure what you mean by “each in a separate blog” but it’s fairly straightforward to create a new blank page template and set that as a front page and in that page pull in group or forum loops.

[@hnla Participant 16 years, 3 months ago]

Rich was asking whether you could confirm that an important stage was definitely being completed correctly as that helps narrow down the areas to troubleshoot.

Using a tool such as phpMyAdmin (MySQL DB manager) find the table called ‘wp_signups’ and confirm that emails that should have been sent and received do indeed have a valid set of entries for registration i.e activation key.

[@hnla Participant 16 years, 3 months ago]

You must validate the page CSS can not correctly parse the DOM / markup and know where to attach it’s rules to when there are markup errors.

You have non legal characters as literals, probably from copy pasting. Run through the major elements token identifiers and make sure they are all correct and proper “” marks

With that corrected you should find that your rulesets now can apply themselves to elements or tokens which they can recognise

[@hnla Participant 16 years, 3 months ago]

This is a theming issue and more specifically – by the sounds of things – a CSS one, but could simply be that the sidebar is trying to render in an incorrect section of the page.

I’m afraid that you would need to supply a lot more detail than you have in order that someone could help, at the moment it’s a ‘How long is a piece of string’ type question.

Tell us the theme your using and as much detail pertaining to type of install and version numbers and preferably a link to the site so that the issue may be observed.

[@hnla Participant 16 years, 3 months ago]

get_stylesheet_directory_uri() should return the URL to your child theme.

As does bloginfo(‘stylesheet_directory’)

One returns result the other needs echoing, other than that is there a preference?

[@hnla Participant 16 years, 3 months ago]

Sorry didn’t read the question carefully enough!

[@hnla Participant 16 years, 3 months ago]

There is a plugin to restrict creating groups; please check through the plugins list under the ‘Extend’ tab

[@hnla Participant 16 years, 3 months ago]

You can send a Site Wide notice to all members; look under ‘Compose’ for checkbox

[@hnla Participant 16 years, 3 months ago]

Great stuff. Must remember that code can’t be copied from the posts for the time being until a proper code block is put in place.

[@hnla Participant 16 years, 3 months ago]

one thing if you copy and pasted from here check that the characters didn’t paste as back ticks or other incorrect characters, so backspace the ‘ and , and enter them from your keyboard.

[@hnla Participant 16 years, 3 months ago]

Your code looks correct and I’m afraid it works for me so at a bit of a loss as to why it’s not working for you.

[@hnla Participant 16 years, 3 months ago]

Try this; replace the line with this version:

jq(‘body#bp-default table.zebra tbody tr:odd, ul#topic-post-list > li:odd’).addClass(‘alt’);

However that does just target the members list you may need to change / remove or add #members-list

Foor that specific page you would want #topic-post-list – I’ve edited above.

[@hnla Participant 16 years, 3 months ago]

Not sure without checking but I don’t think ul lists were taken into account, it shouldn’t be difficult to add that ul li to the jQuery function though.