Forum Replies Created
-
In reply to: [Resolved] BuddyPress doesn’t make pages
Ensure pages exist that can be assigned to BP components, then ensure you have refreshed permalinks and that permalinks are set to anything other than default.
In reply to: BuddyPress doesn’t make pagesPlease do not double post a question it won’t get any faster a response, we see all posts regardless of forum group.
Closing this, continue in:
https://buddypress.org/support/topic/buddypress-doesnt-make-pages-2/
In reply to: Limiting My Blog ContentThis is a WP factor not a Buddypress one. Look into the use of the ‘more tag’ used to split posts where you wish within the post body. The WP codex is your friend for questions like this.
In reply to: Profile fields default is stuck on public@jordas Yes I’ve created a ticket for the issue and it looks like a general issue rather than just affecting you.
In reply to: [Resolved] Small page bug with 1.7betaTry and avoid setting fixed height on elements, it’s not best practise unless there’s a specific reason and the consequences understood.
If the child elements are floated and the parent needs to enclose the floats – not the accepted behaviour of floats – then you must ‘clear’ or ‘contain’ your floats, in many circumstances this can be achieved by adding ‘overflow: hidden’ to the parent to force a new context.
The ‘Smashing Magazine’ article is, unusually, not a particularly good one and is just paraphrasing various classic but old articles; it’s section on float containment is NOT best practise- in fact it’s bad practice and should not be followed.
From a recent post by Boone this duplicate content may be related then to 1.7’s aggressive loading of styles, and scripts theme authors are going to need to add:
add_theme_support(‘buddypress’)
to their themes functions file, preferably hooked to ‘after_theme_setup’
but this will depend on how this theme has been configured to work with BP if at all?
In reply to: Forums Directory Not Showing UpNot a problem; cleared it out.
In reply to: Profile fields default is stuck on publicOff top of my head can’t recall where I was up to in testing ( I’ve created a ticket on the clear issue I found) but check carefully that you have set the option to allow user override on the profile field settings in backend.
In reply to: Member waiting list (beta invites)I took it to be asking whether the requirement was in order to limit the number of people getting a first taste of a beta implementation, i.e with a beta you intend or need to limit the number of people having access to a beta while testing, but other than that I’m not speculating further, we’ll let @ubernaut clarify.
In reply to: Profile fields default is stuck on publicLooking at the function that retrieves this label value it’s checking for an array name that doesn’t exist so is defaulting the label to ‘public’ This probably needs looking into, I’ll raise a ticket.
In reply to: Member waiting list (beta invites)In reply to: [Resolved] Need some help for a customization.:)🙂 Moral of this story then is whom to ask first, be nice if you could provide the eventual solution? might help to have it on record if anyone else using this theme?
In reply to: What do I charge my client?They are now looking at making me a co-founder, because they see how valuable I am at building and maintaining this social community.
Well one of the first rules is avoid clients that attempt to have you work on a promise of fame & riches or want to make you partners or that say “this will be a valuable learning experience for you” or ” it will be great for your portfolio” or ” we know many people in the business we’ll be able to bring you lots of work if you do this for us at a knockdown rate”
If they realise your continued involvement will be essential/useful/necessary then say to them that you will be happy to for a small (or large!) monthly retainer.
There are many contracts all over the web that are development focussed, you can use them as templates but contracts need to be specific to jobs.projects in hand so templates are only guidelines also remember the problem with contracts is that they are meaningless until the point at which you test them in a court of law, if a job gets to that stage then the contract is pretty meaningless it’s simply a set of guidelines for a judge to use to weigh things up.
Look up the term “Work for Hire” and always be clear that you do not work under a “Work to Hire” contract always retain basic rights to the work like attribution even if granting a “Perpetual right to use”
Don’t provide / transfer any work until you have a basic agreement in place of at least a formal acknowledgement that the work is to be paid for.
What should you charge? not really possible to answer that, this industry has few standards it’s too young, developers charge varying rates from $20ph to $200ph it depends on experience, the more formal technical disciplines such as Network Engineers can charge more but they tend to have far more formal and recognized training; so this aspect is largely down to your skill and experience but try and aim no lower than the $40ph mark anything lower than tends to start to devalue the work and effort.
You can’t place a ‘Worth’ on a social community, it’s just code, a site isn’t worth anything until it starts to build it’s value all you can value is the time and effort you put in to building it and the client must understand that.
I would offer a cautionary note lastly, as this reads as one of those situations where the developer comes of worse so proceed with caution, if they are as high powered as you say you need very simple clear contract and also do not be fooled into thinking contracts need to be complex, the more complex the easier it is to have a lawyer break it, and very easily. A good contract is short and to the point, but when/if you draw one up pay attention to basic indemnity clauses, all the bits that say you are responsible for this or that and do not accept anything that even remotely says they can attempt to recover costs from you if they are sued or if their site doesn’t make a million bucks in the first month, in other words your job is to provide valid working code only.
In reply to: [Resolved] Need some help for a customization.:)@mercime |this is a scenario which the BP Template Pack plugin could be used
Shame though; the point of 1.7 compatibility ought to have been to remove the need for template pack once and for all not to allow it to survive – running a custom set of files the scenario for those with moderate coding skills and theme compatibility for those that don’t.
Anyway carry on 🙂
In reply to: BuddyPress CompatibleThis is a public help forum you shouldn’t really be soliciting private help, all help here is on a volunteer basis.
Have you actually bothered to contact Continuum author yet as has been suggested once or twice now? It has been strongly suggested that it is actually a theme issue so it is down to the theme author to try and help really.
We can try and help but frankly have probably exhausted the limits to which we can.
On the duplication issue, there was another thread in which this was happening so I suspect that there is a common cause involved that is being induced by some themes – an extremely long shot but there have been occasions where members loops duplicated odd members this nearly always resolved down to Caching plugins, you shouldn’t be running any until such time as thought necessary on a production site but in case you are deactivate them.
In reply to: [Resolved] Need some help for a customization.:)Hmm your themes page.php has no get_sidebar() call it only juggles a series of dynamic_sidebars depending on what looks to be a per post/page meta value, dynamic sidebars only take their content via widget you the user set from the dashboard widgets page. Not they way I would have built a standard WP template personally, your going to need to add the get_sidebar() function just before get_footer() but that is likely then going to need positioning to fit in your theme and/or the dynamic sidebars adjusting.
For all the work that was done making BP compatible with themes with 1.7 sadly it is going to be a case that it won’t simply and seamlessly work with all especially where they are heavily customised themes or abstracted frameworks that try and depart from WP conventions.
In reply to: Getting BuddyPress WorkingThe template pack approach is all but redundant now with the imminent release of BP 1.7 which will work with any theme without having to go through the template pack process – you will likely not have performed the third step where you need to match the copied BP files now in your theme to your themes standard markup structure.
So if you’re just starting to build your site please do so with the beta release of 1.7 more than likely by the time you’re ready 1.7 RC t will be ready and even if not the beta is very stable and won’t change much other than to fix any little bugs found.
think things may have gone slightly wonky.
ping @johnjamesjacoby
In reply to: Fatal error: Maximum execution time of 90 seconds@konrads thanks for letting us know, good to know theme authors are on the case, would have been nice to know about the initial ticket 4 hours back though 🙂
I’m closing this thread as it’s been tested to not be a BP issue.
In reply to: Fatal error: Maximum execution time of 90 seconds@bphelp yes I asked this from the outset and it was checked; posts 2 & 3
In reply to: Fatal error: Maximum execution time of 90 secondsthis looping occurs for both your groups, create another group, ensure it is public there is some strangeness where the groups seem confused as to whether they are hidden or public stating both at various points.
In reply to: Fatal error: Maximum execution time of 90 secondsIf this is a test/dev site try deleting that group and re-creating.
In reply to: Fatal error: Maximum execution time of 90 secondsSomehow your managing to loop that single group, an infinite loop, this time time generating ~133164 errors
What if any custom code have you added for single groups pages / home.php.
In reply to: Fatal error: Maximum execution time of 90 seconds@mercime The site loaded extremely slowly, so tends to suggest a scripting issue and/or server config, My browser crashing was somewhat unsurprising with my debugging tools and fair few tabs open the browser was simply struggling to parse the massive number of errors causing it to become non responsive while attempting to create a list, ultimately forcing me to kill the browser process or sit there the rest of the day staring at a blank black viewport 🙂
In reply to: Fatal error: Maximum execution time of 90 seconds@mercime that theme is by a name I/we? recognize and in reality a quick download and activation shows a theme that in it’s default OOTB state performs perfectly well, it’s a framework though and as such I haven’t time to reverse engineer it to any great degree to see how it manages all aspects.
@musadiqmarhaban As above I see no particular issues with this theme and that is perhaps important to point out in defence of the authors work, of course there may be hidden issues that might not show simply on activating the base version with no custom configuration, but I tested against 1.7 trunk and also note the theme was updated fairly recently so given those facts and with the greatest respect I would have to point the finger to the customizations to the framework as being the issue and /or plugins running, but in respect of plugins test and ensure all non essential plugins are deactivated so only running the theme and BP this is important to enable narrowing down of the issue.
