Anchora

[Anchora]

wordpress-dashboard..
startpage on bottom, you can do that for the templates

[Anchora]

“page-parts”-folder has some of these files, that affect this. so look for this folder in your child-theme!

especially:
general-forgot-modal.php

was this edited and is present in the child?

[Anchora]

no, both files are not present in the child.

[Anchora]

This reply has been set as private.

[Anchora]

This reply has been set as private.

[Anchora]

nothing to see

greetz from bavarian craft! 😀

[Anchora]

hm sorry abe, but no.
serverside-caching is off.
and i tried several times with newstarting the browser, not only clearing the browsercache..
same results in ff and chrome.

have a look!?

[Anchora]

…. for only one time. couldnt repdroduce it since then, on both ff and chrome.

total-cache is disabled, of course.

&upage=2
this is the part that misses, after clicking on “2”.

but i really dont understand, why it worked ONCE.
only plugin on this page is bp-members-avatar-map, but when deactivated, it still doesnt work.

weird.

[Anchora]

haha now it works 😀

cache-cleaning didnt do it… but restarting did^^

thx

[Anchora]

The problem persists, even after updating everything.
It is 2.4 now, 3-cols.

Searching i.e. for ladies gives 2 pages of results. But when clicking on “2”, this next page returns ALL members, as described above.

[Anchora]

Did the update.
Lost-password-problem is solved indeed.

But that searchresults-mismatch on resultspage 2 still remains.

[Anchora]

copy the sweetdate-folder into
wp-content/themes

[Anchora]

That one here:
https://archived.seventhqueen.com/forums/topic/search-results-mismatch#reply-10443

only tested 1 time, but it seemed, that issue remains

(actually i wouldnt update, if these 2 issues werent present )

[Anchora]

Not yet, because of lots of adjustments.
Thought there would be some easier way.
🙁

But thanks.

Hopefully the related problems with searchpage-2 and lost-password-modal are really solved with this, because actually i’d have no reason to update…

[Anchora]

No, theres no 3-column in that version

[Anchora]

no easy task.
ask google for bp-like + notification
the results will give you a dimension what to do

like here:
http://buddypress.org/support/topic/buddypress-like-notification-hack/#post-169207

[Anchora]

maybe

/home/members/(.*)/profile

or so will work

[Anchora]

Ok I try again:

1. when updating from 2.1 to 2.4, there are several css-issues, though this was all edited in the child. Thats the minor problem. More major is

2. that the right sidebar entirely disappeared after the update. I thought this could be related to our way of implementing the sidebars:
In buddypress-before-wrap.php (in the child) we have inserted this “dynamic_sidebar( ‘sidebara’ );” here:


<aside class=”five columns hide-for-small” id=”leftbar”><?php dynamic_sidebar( ‘sidebara’ ); ?></aside>
<?php /* Before content – action */ ?>


…and quite the equal thing in buddypress-after-wrap.php for the rightbar…

3. When updating to 2.4 but then copying the old 2.1-functions.php to the theme, the issue is gone + right sidebar present again. But doing this makes no sense of course…

[Anchora]

This reply has been set as private.

[Anchora]

you need 2 themes. sweetdate + sweetdate-child. and in the child you only should have the edited files. you activate the child. but when updating, you update the sweetdate.

[Anchora]

put every edited file (with folderstructure) into a new themefolder called sweetdate-child + activate this one

[Anchora]

only edit sweetdate-child!

[Anchora]

it would depend on the plugins you use. in my case:

excluded js:
wp-content/plugins/buddypress-media/app/assets/js/*
http://maps.google.com/maps/api/js/*
wp-content/themes/sweetdate/assets/scripts/*
wp-content/themes/sweetdate/assets/scripts/plugins/jquery.inview.min.js
wp-content/themes/sweetdate/assets/scripts/plugins/jquery.foundation.topbar.js
wp-content/themes/sweetdate/assets/scripts/jquery.foundation.topbar.js
wp-content/themes/sweetdate/assets/scriptsjquery.foundation.mediaQueryToggle.js
wp-content/themes/sweetdate/assets/scripts/jquery.js
wp-content/plugins/buddypress-like/_inc/js/bp-like.dev.js
wp-content/plugins/buddypress-like/_inc/js/bp-like.min.js
wp-content/plugins/bp-like-NEU/_inc/bp-like.js
wp-content/themes/sweetdate/custom_buddypress/_inc/global.js
wp-content/plugins/buddypress/bp-themes/bp-default/_inc/global.js
wp-includes/js/jquery/jquery.js

excluded css:
wp-content/themes/sweetdate/style.css
wp-content/themes/sweetdate-child/style.css
wp-content/themes/sweetdate/assets/styles/font-awesome.min.css
wp-content/themes/sweetdate/framework/options/css/font-awesome.min.css

js: combine only.
both js/css inline.

hope it helps. works nice so far for us.

[Anchora]

I did that. All unwanted changes come from the parents functions.php (which I definately did never edit).
If I update + then copy back the old functions.php, it still works and my right sidebar is present.

btw:
buddypress-before-wrap.php IS different in 2.1 / 2.4.

Would there be another way to implement my sidebars another way than shown above?

[Anchora]

of course i did.
i meant that the corefiles were changed.

[Anchora]

hi abe^^
of course i have changed – the child
but after the update its gone + in relation those mentioned files indeed were different.
bp-before/after..

have a look?

i inserted 2 sidebars, on left + right, which worked well in those 2 files. but the right sidebar, actually placed in bp-after-wrap, is gone now.
the rest would be saved via css, so that would be easy then..

[Anchora]

hi,
you can disable that in wp-dashboard >> settings >> buddypress

[Anchora]

sorry to bother again…
updating to 2.4 crashes the layout. seems to be related to buddypress_before/after_wrap.php
but if not urgently needed, i would spare this at the moment.

as we have the members-avatar-map-plugin running on that page, could that be related?
because when opening the link indirectly, as described above, the results are fine for page 2, but the avatars in the map disappeared.

so would it be easier to solve this possible conflict with the plugin?
or would it be sure that it would work with the update + i rather should edit the caused layout-issues?

thanks again.

you might be happy to hear, that we expect to buy another license for another site.. 😉

[Anchora]

just my 2 cents:

on our page, we have only cdn + minify running! these are the only values, that rise the speedscore. even minify works great, if it is combine-only, with the correct included/excluded files!
(sry robert 😉 )

before using sweetdate, we had different other themes, and i can say that sweetdate is reallyreally fast per-se!

hope this helps a bit 🙂

[Anchora]

the free version of wordfence does that also, as i just found out! 🙂

[Anchora]

http://www.woipadinga.tv

user: squeen
pass: sq125

[Anchora]

the only difference in displaying right/wrong results is the “&upage=2” at the end of the link!
not inserted on direct-click, but available when copied..

doesn’t seem there is special ajax in the source of the results

[Anchora]

via htaccess, for example:
order allow,deny
allow from all
deny from 91.2xxx

or wordfence-pro does that

[Anchora]

display: inline

[Anchora]

sorry to say, but same here, even with the latest update.

when clicking directly the link for page-2 in the results, it gives this adress:

domain.com/nutzer/?field_1=&field_5=&field_6=&field_6_to=&field_2=Weiberl&bs=+

…and as a result, all users are shown.

BUT

when copying this link, or open it in a new tab with rightclick, it gives the correct result for page 2 + with this adress:
domain.com/nutzer/?field_1&field_5&field_6&field_6_to&field_2=Weiberl&bs=+&upage=2

any idea?

[Anchora]

how easy things can be! 😀

thanks abe!

[Anchora]

push!

it is an serious issue, because when having the 20 standardactivities, the page loads sometimes up to 2mb at once!

[Anchora]

http://urbangiraffe.com/plugins/redirection/

http://wordpress.org/plugins/buddypress-login-redirect/

[Anchora]

you install both + activate the child!

and when you edit – you only edit the child-theme..

[Anchora]

#item-buttons { display: inline !important; }

does that work?

[Author]

Posts