Skip to content

Conversation

@deckerweb
Copy link
Contributor

No description provided.

@deckerweb
Copy link
Contributor Author

Yes, Gary, it matters on this area: in load_ functions the unique id string is needed, otherwise it can under some circumstances pull an "random" id from plugin slug etc.

also added domain path to plugin header,
and corrected path in loading function

--> you only need to remove the "old" .pot file "blazer-six-gist-oembed"

@deckerweb
Copy link
Contributor Author

Codestyling Localization plugin has no more error messages with my changes included. Thanks, Dave :)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should "Raw Key" have been left in the translation here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe, don't know how to properly handle this in other languages like German, seems like a special term, and I should change it back - thanks for the feedback :)

@GaryJones
Copy link
Collaborator

Can you please also pull against dev branch, rather than master? Thanks.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does plugin_dir_path() not give the same result as dirname(plugin_basename())?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, does not work - had this with lots of other plugins already, only the change brings it to work.... "load_plugin_textdomain()" requires relative path depending on plugin dir, maybe plugin_dir_path() is absolute or one level to high? It just does not work...

@deckerweb
Copy link
Contributor Author

Just pulled/pushed in dev branch again and made 2nd pull request, also with your suggested changes/corrections

@GaryJones
Copy link
Collaborator

Closing in favour of merged #24.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants