Roll back from 13.1.0-B1 to 13.0.0

What are your problems? on my side, after upgrading to 13.1.0-B1, everything seems to be fine..I meen only cosmetic defects, nothing fundamental...Don't you happen to have outdated third-party modules?

@LeonidS

There are two main issues our members are complaining about

First one is in create person profile where the location widget (the photo below) freezes or demands people to put full address. But often it can't find locations and freezes preventing people from creating a persons profile. That problem didn't exist in previous version. We don't want people to give a complete address - only city and country.

The second problem is in Find person (member in our case). In age range it comes up with a calendar. It didn't do that before ( see image below)

We usually don't upgrade to beta releases. It was my fault, I didn't disable it. How do I roll back without losing the members who have signed up since the upgrade?

Thank you so much in advance for your help.

Kind regards

Finn

the location field is giving trouble even without the upgrade - I haven't upgraded as yet. I removed that field for now. not sure about your age range field.

Since upgrade to 13.1.0 - B1 error messages are sent 2/3 times a day

1. Database error in xyxy... Mysql error:Table 'mainsite_una.bx_groups_fans' doesn't exist
2. And a message by the cron daemon

We have got some error messages as well after upgrading

.bx-form-element .bx-form-value .bx-form-input-location-street_number, .bx-form-element .bx-form-value .bx-form-input-location-street {

display: none;

}

And what about UNA hosted Cloud?

Hello, check this, if you have this setting, you must have the cursor and not the calendar. I'm not sure anymore, but it seems to me that the update reversed my setting.

If you use Nominatim, for the location fields problem, you can fix the problem like this.

In /inc/classes/BxDolLocationFieldNominatim.php

Replace

$sRet = $oForm->getTemplate()->parseHtmlByName('location_field_plain_auto.html', $aVars);
        }
        else {
            $aFields = array(
                'lat' => array('type' => 'hidden'),
                'lng' => array('type' => 'hidden'),
                'street_number' => array('type' => 'text', 'ph' => _t('_sys_location_ph_number')),
                'street' => array('type' => 'text', 'ph' => _t('_sys_location_ph_street')),
                'city' => array('type' => 'text', 'ph' => _t('_sys_location_ph_city')),
                'state' => array('type' => 'text', 'ph' => _t('_sys_location_ph_state')),
                'zip' => array('type' => 'text', 'ph' => _t('_sys_location_ph_zip')),
                'country' => array('type' => 'select'),
            );


By

$sRet = $oForm->getTemplate()->parseHtmlByName('location_field_plain_auto.html', $aVars);
        }
        else {
            $aFields = array(
                'lat' => array('type' => 'hidden'),
                'lng' => array('type' => 'hidden'),
                'street_number' => array('type' => 'hidden', 'ph' => _t('_sys_location_ph_number')),
                'street' => array('type' => 'hidden', 'ph' => _t('_sys_location_ph_street')),
                'city' => array('type' => 'text', 'ph' => _t('_sys_location_ph_city')),
                'state' => array('type' => 'text', 'ph' => _t('_sys_location_ph_state')),
                'zip' => array('type' => 'text', 'ph' => _t('_sys_location_ph_zip')),
                'country' => array('type' => 'select'),
            );

So just put "hidden" the fields you don't want to see

But it would be nice to have a high precision/low precision option because not everyone wants to ask for the precise address.

I noticed this too, sometimes it displays but not all the time.

That worked fine before

It certainly look that way. Will check our installation

Exactly! For our members, town/city, state/province, and country would be sufficient

yes it did, but I don't know when it stopped working, maybe in the previous update? because I haven't updated to the latest one

It worked in 13.0