I have been doing some work with Extgallery recently and found that the module will automatically use the filename if no photo title is entered. This is useful, but if you want to force users to enter a title you can change the following.

In public_upload.php at about line 68, simply change FALSE at the end of the line to TRUE (as shown) and the Xoops form feature will make the field required.



It's a good idea to make uploading a photo a requirement, so you can make the change again just below at around line 74:



The second change might be a better default IMHO.

PK

For anyone new to the Profile module (me included) to force the multi-step registration you need to open the 'Registration Steps' screen in the module admin and click on the green tick in the 'Save after step' column in the 'Basic' row to turn it into a red cross. Otherwise, the validation email will be sent once the first form is completed, even if the person abandons the second 'advanced' form without completing any of it.

I recently read a question asking if the 'upload' and 'user album' links could be added to the main page of Extgallery instead of it being visible only in the main menu block. I had a requirement to do this myself recently, so I hope this may help someone else. It's pretty easy (this is for Extgallery version 1.11 updated by Zoullou + Xoops 2.5.5). Obviously, create backups first.

Firstly, in 'extgallery/index.php' add the following, before the footer include line:




Next, add the links to 'templates\extgallery_index.html'. You can style these links as required, or turn them into buttons.



Finally, add a new language definition to 'language\english\main.php':



HTH

**EDIT

Sorry, missed out a step in the above.

You will during the process of getting a new key be asked to choose an API. The one you want is 'Google Maps JavaScript API'.

You can access all the APIs from the 'Library' menu option in the left sidebar.

Peekay

Google Maps API Keys are back

To embed Google Maps in a website, webmasters had to register for a free 'API Key' on the Google developers website. Then, Google changed the rules and for a while you could embed maps without a key. Now, from June 2016, API keys are back.

To get keys for your domains that use a Google maps module (you need one for each domain AFAIK) go to:

https://console.developers.google.com

Log in with your Google account credentials. In the API Manager screen - to the right of the Google API logo - you will see a drop-down menu of API projects. If you had registered a key sometime in the distant past, you may find that you already have a project called 'API Project' which is the name given to legacy keys.

Getting a new key

Getting a new key is a two step process. First, you need to create a new project/key combination. To do this, select the aforementioned drop-down menu, choose 'Create Project' then follow the prompts. At some point a window will appear with the key which you can copy. You will need to paste it into a module preference field, or hard-code it into the URL that calls Google Maps.

Step two is to register your site domain with Google. To do this:

* Ensure the correct project is selected in the drop-down menu.
* Select the 'Credentials' option in the left sidebar.
* Click once on the key (the default name is 'Browser key').
* Under the section 'Accept requests from these HTTP referers' do the following:

1) In the empty field, enter the word

Quote:
and press 'Save' (this enables localhost map development)

2) In the new empty field that then appears, enter the actual site URL including the wildcards, e.g.

Quote:
It can take a few minutes for the changes to take effect.

Code changes

There have also been some changes to the way Google maps is accessed. Most importantly, you will need to change the primary script source URL from:

Quote:
to:
Quote:
Some of the syntax has also changed, e.g.

Quote:
Quote:
There are more replacement pairs listed on the Google developers website, but these seem to be the significant ones. You may also need to remove some references to deprecated classes to prevent Javascript console errors. Running Firebug in Firefox will display errors from Google if their map API is unhappy about something.

For example, the addControl() method is deprecated, so in the module that I use I had to comment out:

Quote:
The default map controls are now enabled by default, so map navigation wasn't affected.

There's a good guide to implementing the update at:

https://developers.google.com/maps/articles/v2tov3

HTH */

... and some more. I should point out that I am using Xoops 2.5.5 so the CSS identifiers may have changed in later versions.

This is my search CSS. Obviously the values may not apply to your theme, but it shows the targets. A height and width setting for the checkbox input may change the box size, although I haven't tried it.

I have been working with the xbootstrap theme recently and it is really good, however the checkboxes for selecting modules on the 'search results' page (and everywhere else for that matter) are presented in a horizontal line. The line doesn't break when the page is viewed on a mobile phone, so I hacked the code to display checkboxes underneath each other.

This is bad practice, invalid HTML and of course it affects every checkbox array on the site... but it makes the boxes easy to select on a phone and they don't break out of the viewport.


/class/xoopsform/formcheckbox.php

Around line 208

Change:



to:

The lack of any sort order in the TinyMCE image-manager plugin has bugged me for years, but I have just lived with it.... until now!

Quote:

Added the above fix at around line 470.

It is a little late (6 years) but many thanks elpaksu

That is completely unacceptable. Very disappointing to see this kind of response. You should discuss this with your other moderators.