Yes, those are to be expected with outdated plugins. Grid's changelog clearly indicated that this release (1.30300.1290) required most plugins to be updated. I personally updated all of the plugins hosted with open repositories here on WowAce/CurseForge, and sent PMs to the authors of plugins on WoWI, or with closed repositories. The changes were made to Grid on December 27th, and the release wasn't pushed until April 15th -- plugin authors had over four months to update their plugins.
GridManaBars, according to its changelog, was updated for the changes on December 28th. Make sure you have the latest version.
If no updates are available for those plugins, and those are the only errors you're seeing, you should be able to fix them by adding this to the top of each file indicated:
I went ahead and committed fixes to GridManaBars, GridSideIndicators, GridDynamicLayout, and GridStatusLifebloom. Not sure how I missed that many when I committed fixes back in December or January.
I can't do anything about GridIndicatorCornerText or GridIndicatorSideText, since they don't have repositories here. Pester their authors.
Hmm. I will stay with the version of all these that works then. Is there any reason why we should upgrade to the latest version of Grid? It just removes unnecessary globals, right? Makes sense for most to just stick with the version from a couple days ago that works with the Grid plugins...until they are all updated.
It's marked as Abandoned; I'm not touching it. However, it looks like someone already committed a fix, the day after the changes were made to Grid back in December. Grab the latest alpha from the page you linked.
Hmm. I will stay with the version of all these that works then. Is there any reason why we should upgrade to the latest version of Grid? It just removes unnecessary globals, right? Makes sense for most to just stick with the version from a couple days ago that works with the Grid plugins...until they are all updated.
No. I wouldn't have pushed a release version simply to remove some globals... and I was going to do that, I'd have pushed the release 4 months ago when I removed the globals. The current release contains tons of bugfixes. Rather than sticking your head in the sand and using an outdated and unsupported version, or complaining to me, you should complain to the plugin authors who had over 4 months to make a very minor change to their plugins and didn't bother to do it.
I'm also pretty confused by the fact that I pushed the release version a week ago, but nobody seemed to update until yesterday. Did it really take a week for the release version to sync to Curse.com?
It's marked as Abandoned; I'm not touching it. However, it looks like someone already committed a fix, the day after the changes were made to Grid back in December. Grab the latest alpha from the page you linked.
Tried with latest Grid r1293 and the last Grid_QuickHealth r35 and still appears the message
Message: ...terface\AddOns\Grid_QuickHealth\Grid_QuickHealth.lua line 15:
attempt to index global 'GridStatus' (a nil value)
Debug:
[C]: ?
...terface\AddOns\Grid_QuickHealth\Grid_QuickHealth.lua:15: in main chunk
being abandoned i guess we have to wait something :)
I already fixed that one, back in January. Grab the latest alpha from the project page; its author hasn't pushed a release version since then.
I was already using the alpha and it wasn't fixed (I checked the source before I posted here).
It's irrelevant now anyway as the author made the required change today.
I notified the author of GridIndicatorCornerText and SideText. Phanx the one line fix you suggested didn't work. I placed it at the top of the GridIndicatorCornerText.lua file, for ex, and ended up with this error:
1x ...\GridIndicatorCornerText\GridIndicatorCornerText.lua:17: attempt to index global 'GridFrame' (a nil value):
I was already using the alpha and it wasn't fixed (I checked the source before I posted here).
Unfortunately several plugin authors reverted the commits I made, whether it was intentional or not. I know at least a few were intentional, though I don't understand why they don't just close their repository if they don't want anyone other than themselves committing anything, especially when the commit is a required change to keep their addon working, and doesn't affect the addon's functionality from a user standpoint. :|
Is there a replacement for the old GridAlert that has been working without errors until the latest Grid builds with global changes?
Not that I know of, although the same should apply. Any globals that the plugin complains about being unable to find should be fixable; if the error says it can't find GridMagicModule, add:
local GridMagicModule = Grid:GetModule("GridMagicModule")
... at the top of the file throwing the error. Repeat until no more errors occur.
It's been ages since I looked at GridAlert, but it may be looking for specific status module (eg. GridStatusAura) which are slightly different in that they are sub-modules of GridStatus, so:
local GridStatusAura = Grid:GetModule("GridStatus"):GetModule("GridStatusAura")
If you post the specific errors you're seeing from GridAlert, I can tell you exactly what to add. It's marked as abandoned though, so as with the other plugin, I'm not going to make any commits to its repository. Better in general to let it stay broken if nobody is maintaining or supporting it.
No changes have been made that should break any plugins, unless those plugins were using Grid's localized strings instead of supplying their own. The only plugin I know of that was doing this was GridStatusRes, which I updated at the same time I committed that change to Grid. The purpose of the change was to remove the AceLocale-2.2 library, which was both unnecessary (a custom solution is simpler anyway) and inefficient (for the vast majority of users, Grid is the only addon loading it or any other Ace2 libraries).
Aside from that, the other change made in the last few days was to add support for dual-spec profile swapping, but this shouldn't have any effect on any plugins, since it doesn't do anything that a user manually changing the profile wouldn't do. Even if you're using a plugin that automatically changes your profile based on certain conditions, you shouldn't have any problems, especially since the dual-spec feature is disabled by default.
What specific problems are you seeing, and which revision are you using?
No changes have been made that should break any plugins, unless those plugins were using Grid's localized strings instead of supplying their own. The only plugin I know of that was doing this was GridStatusRes, which I updated at the same time I committed that change to Grid. The purpose of the change was to remove the AceLocale-2.2 library, which was both unnecessary (a custom solution is simpler anyway) and inefficient (for the vast majority of users, Grid is the only addon loading it or any other Ace2 libraries).
Aside from that, the other change made in the last few days was to add support for dual-spec profile swapping, but this shouldn't have any effect on any plugins, since it doesn't do anything that a user manually changing the profile wouldn't do. Even if you're using a plugin that automatically changes your profile based on certain conditions, you shouldn't have any problems, especially since the dual-spec feature is disabled by default.
What specific problems are you seeing, and which revision are you using?
Please rollback to enable the dependency "AceLocale-2.2". This is the source of current problems in some third party addons. Until all developers decide to include the missing dep or use a custom solution (like you did).
Thanks in advance.
GridManaBars, according to its changelog, was updated for the changes on December 28th. Make sure you have the latest version.
If no updates are available for those plugins, and those are the only errors you're seeing, you should be able to fix them by adding this to the top of each file indicated:
local GridStatus = Grid:GetModule("GridStatus")-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorGridSideIndicators also wasn't updated, yet.
I can't do anything about GridIndicatorCornerText or GridIndicatorSideText, since they don't have repositories here. Pester their authors.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumWith this latest releases keep giving the "attempt to index global 'GridStatus' (a nil value)"
I already fixed that one, back in January. Grab the latest alpha from the project page; its author hasn't pushed a release version since then.
It's marked as Abandoned; I'm not touching it. However, it looks like someone already committed a fix, the day after the changes were made to Grid back in December. Grab the latest alpha from the page you linked.
No. I wouldn't have pushed a release version simply to remove some globals... and I was going to do that, I'd have pushed the release 4 months ago when I removed the globals. The current release contains tons of bugfixes. Rather than sticking your head in the sand and using an outdated and unsupported version, or complaining to me, you should complain to the plugin authors who had over 4 months to make a very minor change to their plugins and didn't bother to do it.
I'm also pretty confused by the fact that I pushed the release version a week ago, but nobody seemed to update until yesterday. Did it really take a week for the release version to sync to Curse.com?
Tried with latest Grid r1293 and the last Grid_QuickHealth r35 and still appears the message
Message: ...terface\AddOns\Grid_QuickHealth\Grid_QuickHealth.lua line 15:
attempt to index global 'GridStatus' (a nil value)
Debug:
[C]: ?
...terface\AddOns\Grid_QuickHealth\Grid_QuickHealth.lua:15: in main chunk
being abandoned i guess we have to wait something :)
But, the fix I described in my post further up this page should work for you.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIt's irrelevant now anyway as the author made the required change today.
1x ...\GridIndicatorCornerText\GridIndicatorCornerText.lua:17: attempt to index global 'GridFrame' (a nil value):
EDIT:
Just add the below to fix these...
local GridFrame = Grid:GetModule("GridFrame")replace line 4:
with:
local GridFrame = Grid:GetModule("GridFrame")And add the GridStatus part that Phanx called out a few posts earlier. Seems to be ok.
Unfortunately several plugin authors reverted the commits I made, whether it was intentional or not. I know at least a few were intentional, though I don't understand why they don't just close their repository if they don't want anyone other than themselves committing anything, especially when the commit is a required change to keep their addon working, and doesn't affect the addon's functionality from a user standpoint. :|
Not that I know of, although the same should apply. Any globals that the plugin complains about being unable to find should be fixable; if the error says it can't find GridMagicModule, add:
local GridMagicModule = Grid:GetModule("GridMagicModule")... at the top of the file throwing the error. Repeat until no more errors occur.
It's been ages since I looked at GridAlert, but it may be looking for specific status module (eg. GridStatusAura) which are slightly different in that they are sub-modules of GridStatus, so:
local GridStatusAura = Grid:GetModule("GridStatus"):GetModule("GridStatusAura")If you post the specific errors you're seeing from GridAlert, I can tell you exactly what to add. It's marked as abandoned though, so as with the other plugin, I'm not going to make any commits to its repository. Better in general to let it stay broken if nobody is maintaining or supporting it.
Yeah, hence the "if those are the only errors you're getting" qualification. :p
Aside from that, the other change made in the last few days was to add support for dual-spec profile swapping, but this shouldn't have any effect on any plugins, since it doesn't do anything that a user manually changing the profile wouldn't do. Even if you're using a plugin that automatically changes your profile based on certain conditions, you shouldn't have any problems, especially since the dual-spec feature is disabled by default.
What specific problems are you seeing, and which revision are you using?
Please rollback to enable the dependency "AceLocale-2.2". This is the source of current problems in some third party addons. Until all developers decide to include the missing dep or use a custom solution (like you did).
Thanks in advance.
I actually would hold off on tagging a release, since Grid.L only exists in alpha versions of Grid right now.
Though, I will probably tag a new Grid release fairly soon to push out the dual-spec support, once translators do their thing.
thanks in advance