Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MapObj->save ignores Symbol ANCHORPOINT property #5073

Closed
traffin opened this issue Feb 18, 2015 · 4 comments
Closed

MapObj->save ignores Symbol ANCHORPOINT property #5073

traffin opened this issue Feb 18, 2015 · 4 comments

Comments

@traffin
Copy link

@traffin traffin commented Feb 18, 2015

Symbols with ANCHORPOINT defined in will be saved without ANCHORPOINT when using MapObj->save method in PHP/MapScript

Version: MapServer 6.2.1 on Windows

@traffin traffin changed the title PHP/MapScript MapObj->save ignore Symbol Anchorpoint proporty PHP/MapScript MapObj->save ignore Symbol ANCHORPOINT property Feb 18, 2015
@tbonfort tbonfort changed the title PHP/MapScript MapObj->save ignore Symbol ANCHORPOINT property MapObj->save ignores Symbol ANCHORPOINT property Feb 18, 2015
@tbonfort tbonfort added this to the 7.0 Release milestone Feb 18, 2015
@tbonfort tbonfort self-assigned this Feb 18, 2015
tbonfort added a commit that referenced this issue Feb 18, 2015
@tbonfort
Copy link
Member

@tbonfort tbonfort commented Feb 18, 2015

Fixed for 7.0, remilestoning to 6.4.2

@tbonfort tbonfort modified the milestones: 6.4.2 release, 7.0 Release Feb 18, 2015
@traffin
Copy link
Author

@traffin traffin commented Feb 18, 2015

Thanks!
Do you know if there is a way to easily patch windows binaries please?

@tbonfort
Copy link
Member

@tbonfort tbonfort commented Feb 18, 2015

You'll have to backport the patch and recompile

@mapserver-bot
Copy link

@mapserver-bot mapserver-bot commented Feb 23, 2016

This is an automated comment

This issue has been closed due to lack of activity. This doesn't mean the issue is invalid, it simply got no attention within the last year. Please reopen with missing/relevant information if still valid.

Typically, issues fall in this state for one of the following reasons:

  • Hard, impossible or not enough information to reproduce
  • Missing test case
  • Lack of a champion with interest and/or funding to address the issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.