×

Notice

The forum is in read only mode.
Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC: Update from 3.4 to 3.5 brought two new bugs

Update from 3.4 to 3.5 brought two new bugs 11 years 5 months ago #21755

  • Krx
  • Krx's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 10
  • Thank you received: 0
Hi

Few hrs ago I've updated from v 3.4 to v3.5 and now when hotspot is opened in frontend via menu item, Firefox shows this JS error:

Timestamp: 14.7.2013. 23:30:24
Error: TypeError: b is undefined
Source File: http://localhost/websitename/media/com_hotspots/js/modules/hotspot.js
Line: 95

Also in backend it seems that default zoom level set in hotspot settings is not taken into account, maps is always zoomed out. Also FF shows this JS error in hotspots backend in dashboard:

Timestamp: 14.7.2013. 23:32:23
Error: TypeError: markers.filter is not a function
Source File: http://localhost/websitename/media/com_hotspots/js/moo/Map.Marker.js
Line: 135

Map shown in dashboard or in adding or editing hotspot is fully zoomed out.
"Startzoom of the map" setting is set to 15

I've cleared all Joomla and Browser caches.

Joomla 2.5.11

Also, a hint: please add option to copy category or hotspot. It makes adding new hotspots faster

Regards

Update from 3.4 to 3.5 brought two new bugs 11 years 5 months ago #21756

  • Faris M Hayek
  • Faris M Hayek's Avatar
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 19
  • Thank you received: 0
Exact same issue.

Update from 3.4 to 3.5 brought two new bugs 11 years 5 months ago #21757

  • Faris M Hayek
  • Faris M Hayek's Avatar
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 19
  • Thank you received: 0
My map doesnt display from a menu item when all the categories are selected.

Update from 3.4 to 3.5 brought two new bugs 11 years 5 months ago #21759

  • Daniel Dimitrov
  • Daniel Dimitrov's Avatar
  • Offline
  • Administrator
  • Administrator
  • Posts: 9618
  • Karma: 155
  • Thank you received: 1081
Hey guys,

@Krx - go to the hotspots menu and check the map center setting -> is it set to center by start position/zoom or is it set to center by marker boundary? change it to start position/zoom and save the menu.

Also the Js error in frontend is a known issue and it has been there since version 3 - I can't always reproduce it and that is why I have no idea why it happens. What I know is -> it doesn't impact the map behavior in any way.


@Faris - I replied in your own thread.

Daniel

Update from 3.4 to 3.5 brought two new bugs 11 years 5 months ago #21760

  • Krx
  • Krx's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 10
  • Thank you received: 0
Hi Daniel


Thanks for suggestion, but doesn't it cover only fronted map? On frontend map zoom is shown OK, and I like that it's centered by category marker bounds.

Problem is in backend - all maps displayed there are fully zoomed out. Whenever I need to edit or add new hotspot I need to manually zoom in to 16-17, in order to place marker correctly. This makes process of adding new hotspots difficult.

This issue wasn't here in version 3.4

I tried your suggestion, but it changes nothing in backend.

Regards

Update from 3.4 to 3.5 brought two new bugs 11 years 5 months ago #21761

  • Daniel Dimitrov
  • Daniel Dimitrov's Avatar
  • Offline
  • Administrator
  • Administrator
  • Posts: 9618
  • Karma: 155
  • Thank you received: 1081
Hm, strange. I haven't changed anything related to that. I'll check and will let you know.

Update from 3.4 to 3.5 brought two new bugs 11 years 5 months ago #21763

  • Daniel Dimitrov
  • Daniel Dimitrov's Avatar
  • Offline
  • Administrator
  • Administrator
  • Posts: 9618
  • Karma: 155
  • Thank you received: 1081
Okay, you are right.
I've fixed the issue in the latest dev release:
compojoom.com/component/ars/repository/dev-hotspots

Now per default we use the center and zoom set in the global configuration.

Regards,
Daniel
The following user(s) said Thank You: Krx

Update from 3.4 to 3.5 brought two new bugs 11 years 5 months ago #21764

  • Krx
  • Krx's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 10
  • Thank you received: 0
Hi

Yep it worked, thanks.
For others: download this one (git21963dd(Alpha)).
At 1st I tried 1st version (both shared same time stamp) and that one was without fix.


Suggestions: Could you add these options in settings?

1. An option to have "Sticky marker" as No by default.
Google often adds wrong addresses in smaller cities or rural areas.
I for example need to set it as No for most of our hotposts.
Option to set it to No by default would save 2 mouse clicks for each new hotspot


2. Disable map in backend dashboard
Someone with a lot of hotspots might want this disabled,
no point to show this in admin area.


Regards

Update from 3.4 to 3.5 brought two new bugs 11 years 5 months ago #21765

  • Daniel Dimitrov
  • Daniel Dimitrov's Avatar
  • Offline
  • Administrator
  • Administrator
  • Posts: 9618
  • Karma: 155
  • Thank you received: 1081
Hm, strange that there are 2 releases...

1. You could modify:
administrator/components/models/form/marker.xml

look for the sticky field and set the default to 0.

Do the same in components/models/form/marker.xml for the frontend.

2. Just go to the module manager -> administrator and disable the hotspots module that creates the map. :)

Regards,
Daniel
  • Page:
  • 1
Time to create page: 0.154 seconds