Create map from contexte from v2025.01.xx

[Martin DELSINNE]

Hi,

Surprisingly, since I switched to the 2025.01.xx branch, I can no longer create a map from a context. In fact, I also can't edit a context anymore—unless I manually access it via the URL using the context ID.

There are no longer any buttons or options to create a map from a context...

Has anyone else encountered this issue or have any idea what might be causing it?

Thanks in advance!

[Martin DELSINNE]

I was able to create a map from a context by opening the context, adjusting my map, and then using "Save As." This successfully creates a new map based on the context. However, I don't understand how to modify an existing context. How can I change the configuration of the widgets so that it impacts all maps created from that context?

Any help or insight would be greatly appreciated!

[Stefano Bovio]

Dear Martin,

the new version 2025.01.xx adds a new plugin called EditContext that shows two new button on the context resource card when a user has edit permissions,

Could you verify if your localConfig.json is updated? 

You can take a look to the migration guideline here for the needed changes in localConfig.json for version 2025.01.xx

Hope this helps,
Stefano

--
You received this message because you are subscribed to the Google Groups "mapstore-developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mapstore-develo...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/mapstore-developers/12ba2e11-0c1e-4e18-9823-a016b6b4ad7an%40googlegroups.com.

--

Regards,

Stefano Bovio

==

GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

==

Stefano Bovio

Frontend Software Engineer

GeoSolutions Group
phone: +39 0584 962313

fax:     +39 0584 1660272

mob:   +39  333 8128928

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

-------------------------------------------------------

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

[Tobia Di Pisa]

Dear Martin,

2025.01.xx brings some changes also on this workflow to ensure better consistency on map contexts creation by using the right context setup.

• To edit a context you have to open the context wizard having right permissions for doing that as usual
• To create a map from a context you have to open the context and then create the map as usual.  The option to create a map context directly from home by selecting a context from the list is no longer available because it was not enough consistent. Now you have to use the specific button mentioned by Stefano
• To edit an existing context map including changes, adding/modify widgets etc., you have to open it and save as usual

Regards,

     Tobia Di Pisa

--

You received this message because you are subscribed to the Google Groups "mapstore-developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mapstore-develo...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/mapstore-developers/12ba2e11-0c1e-4e18-9823-a016b6b4ad7an%40googlegroups.com.

--

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.
==

Dott. Ing. Tobia Di Pisa
Technical Lead / Project Manager

GeoSolutions Group
phone: +39 0584 962313

mobile: +39 340 1781783
fax:      +39 0584 1660272

https://www.geosolutionsgroup.com/
http://twitter.com/geosolutions_it
-------------------------------------------------------

[Martin DELSINNE]

Thank you for your detailed replies.
However, I'm still facing the same issue. I'm logged in as an admin, but I still don't see all the buttons as expected (e.g., Edit and Delete).

I even started from scratch, with an up-to-date localConfig.json (including the EditContext plugin properly declared), an updated pluginsConfig.json, ran npm install, and everything else.

Despite that, the Edit and Delete buttons are missing. There are no errors in the console, and the build process completes successfully...

[Martin DELSINNE]

  I also added a console.log in EditContext.jsx

function EditContext({

    resource,

    component,

    target

}) {

    const Component = component;

    console.log('EditContext', resource, component, target);

    if (resource?.canEdit && resource?.category?.name === 'CONTEXT') {

        return (

            <>

                <Component

                    glyph="add-map"

                    iconType="glyphicon"

                    labelId="resourcesCatalog.createMapFromContext"

                    square

                    href={`#/viewer/new/context/${resource.id}`}

                    target={target}

                />

                <Component

                    glyph="pencil"

                    iconType="glyphicon"

                    labelId="contextManager.editContextTooltip"

                    square

                    href={`#/context-creator/${resource.id}`}

                    target={target}

                />

            </>

        );

    }

    return null;

}

EditContext {advertised: true, category: {…}, creation: '2025-06-19T14:15:40.032+02:00', creator: 'admin', description: '', …}@extras: {info: {…}, status: {…}}info: {title: 'MyContext', icon: {…}, thumbnailUrl: undefined, viewerPath: '/context/MyContext', viewerUrl: '#/context/MyContext'}icon: {glyph: 'cogs'}thumbnailUrl: undefinedtitle: "MyContext"viewerPath: "/context/MyContext"viewerUrl: "#/context/MyContext"[[Prototype]]: Objectstatus: {items: Array(0)}items: []length: 0[[Prototype]]: Array(0)[[Prototype]]: Object[[Prototype]]: Objectadvertised: trueattributes: {detailsSettings: {…}}category: id: 6name: "CONTEXT"[[Prototype]]: Objectcreation: "2025-06-19T14:15:40.032+02:00"creator: "admin"description: ""editor: "admin"id: 15lastUpdate: "2025-06-19T14:16:34.178+02:00"name: "MyContext"[[Prototype]]: Objectconstructor: ƒ Object()hasOwnProperty: ƒ hasOwnProperty()isPrototypeOf: ƒ isPrototypeOf()propertyIsEnumerable: ƒ propertyIsEnumerable()toLocaleString: ƒ toLocaleString()toString: ƒ toString()valueOf: ƒ valueOf()__defineGetter__: ƒ __defineGetter__()__defineSetter__: ƒ __defineSetter__()__lookupGetter__: ƒ __lookupGetter__()__lookupSetter__: ƒ __lookupSetter__()__proto__: (…)get __proto__: ƒ __proto__()set __proto__: ƒ __proto__() ({
  glyph,
  iconType,
  labelId,
  onClick,
  square,
  variant,
  borderTransparent,
  loading,
  ...props
}) => {
  function handleOnClick(event) {
    event.stopPropagation();
    if (onClick) {… undefined


  I noticed that my resource object doesn't have a canEdit property  

[Martin DELSINNE]

Problem solved

It turned out that the issue was caused by Maven and its dependencies—specifically the pom.xml file.

To fix it, I created a new project from version v2025.01.00, then compared the pom.xml at the root of my project, as well as the one in [PROJECT_MAPSTORE]/web/pom.xml, with the ones from the newly generated project.
That’s when I noticed they weren’t exactly the same, particularly the version numbers of several dependencies. So I updated my project to match the new one.

Finally, after running mvn clean install and then npm start, it worked! I now have the Edit, Delete, and other buttons visible again.

  Thanks for your help—it pointed me in the right direction!