Thanks for the great info Blair. That language file in folder 5 sorts out most of the issues.
I have downloaded this three times from the site here and have installed, removed, activated, and deactivated it through my site a good handful of times. Something is wrong, broke, missing, or something else entirely with the language, I guess.
I see that a few other people have had similar issues like this when trying to use it. Why is this not fixed for all? I see it's requested to have server access, but, really, why is that necessary? What is being changed, tweaked?
After activation, I cannot change anything with the language.
When going into the plugin after activation for tweaks, this is what it shows me (as well as what is displayed externally on the site to members):
iclassifieds+admin_tab_general_title
iclassifieds+admin_category_tab_title
iclassifieds+admin_pending_approval
iclassifieds+admin_expired_items
iclassifieds+admin_item_approval
iclassifieds+admin_results_per_page
iclassifieds+admin_default_currency
iclassifieds+enable_one_currency
iclassifieds+admin_condition_types
iclassifieds+admin_plugin_theme
iclassifieds+admin_allowed_image_count
iclassifieds+admin_preview_image_size
iclassifieds+enable_multi_categories
iclassifieds+enable_3d_cloud_categories
iclassifieds+enable_disclaimer_notice
iclassifieds+support_bitcoin
I have downloaded this three times from the site here and have installed, removed, activated, and deactivated it through my site a good handful of times. Something is wrong, broke, missing, or something else entirely with the language, I guess.
I see that a few other people have had similar issues like this when trying to use it. Why is this not fixed for all? I see it's requested to have server access, but, really, why is that necessary? What is being changed, tweaked?
After activation, I cannot change anything with the language.
When going into the plugin after activation for tweaks, this is what it shows me (as well as what is displayed externally on the site to members):
iclassifieds+admin_tab_general_title
iclassifieds+admin_category_tab_title
iclassifieds+admin_pending_approval
iclassifieds+admin_expired_items
iclassifieds+admin_item_approval
iclassifieds+admin_results_per_page
iclassifieds+admin_default_currency
iclassifieds+enable_one_currency
iclassifieds+admin_condition_types
iclassifieds+admin_plugin_theme
iclassifieds+admin_allowed_image_count
iclassifieds+admin_preview_image_size
iclassifieds+enable_multi_categories
iclassifieds+enable_3d_cloud_categories
iclassifieds+enable_disclaimer_notice
iclassifieds+support_bitcoin
I have downloaded this three times from the site here and have installed, removed, activated, and deactivated it through my site a good handful of times. Something is wrong, broke, missing, or something else entirely with the language, I guess.
I see that a few other people have had similar issues like this when trying to use it. Why is this not fixed for all? I see it's requested to have server access, but, really, why is that necessary? What is being changed, tweaked?
After activation, I cannot change anything with the language.
When going into the plugin after activation for tweaks, this is what it shows me (as well as what is displayed externally on the site to members):
iclassifieds+admin_tab_general_title
iclassifieds+admin_category_tab_title
iclassifieds+admin_pending_approval
iclassifieds+admin_expired_items
iclassifieds+admin_item_approval
iclassifieds+admin_results_per_page
iclassifieds+admin_default_currency
iclassifieds+enable_one_currency
iclassifieds+admin_condition_types
iclassifieds+admin_plugin_theme
iclassifieds+admin_allowed_image_count
iclassifieds+admin_preview_image_size
iclassifieds+enable_multi_categories
iclassifieds+enable_3d_cloud_categories
iclassifieds+enable_disclaimer_notice
iclassifieds+support_bitcoin
To spell this out here is the process that devs follow when updating the lang in a plugin.
If they have a new text variable, they create that variable in the language file using the dev-tools portion of admin section using this process
https://wiki.oxwall.com/faq:site_configuration:manage_languages?s[]=dev&s[]=tools
Then when the dev is done with that process they MUST remember to export their lang file for the plugin and then upload it to the server of their dev version and overwrite the langs.zip file. This will allow them to use the most current copy of the langs file on their dev copy.
They also need to remember to set the new import value for the new langs.zip file in the update folder of the update so that when a user updates they get the new lang.zip file imported to thier copy.
I suspect that the dev either forgot to include the lang.zip import command in their update folder file or they saved their dev copy without exporting the current lang.zip version and including it in their released copy.
Either way the solution is this:
1. open up the last update folder for the plugin and look inside the update.php file... there should be a command that looks like this:
OW::getLanguage()->importPluginLangs(OW::getPluginManager()->getPlugin('PLUGINNAME')->getRootDir().'update/NUMBER/langs.zip', 'PLUGINNAME');
PLUGINNAME is the name of your plugin... and the NUMBER is the number of the update folder... if the folder is named 7 then there should be a 7 for NUMBER
If that code is not in that file then add it... the plugin name should be in lowercase.
Make sure there is a langs.zip file in the update folder as well. If it is not there then you need to download a fresh copy of your plugin from the oxwall server and upload the langs.zip folder from the plugin root to the update folder.
Then uninstall the plugin and reinstall, clear your cache and you should now have the missing lang values.
If that code is there and it has the right number and plugin name, then that means that the dev forgot to update with the right copy of the langs.zip file... In this case the fix is somewhat longer....
First i would download the plugin from your plugins list, then i would take the langs.zip file from the root of the plugin download and stick it into the update folder and also overwrite the langs.zip file in the plugin root on the server as well.
To be cliear here, when an update is issued on a plugin the plugin root langs.zip file and the update folder (number of release) langs.zip file should be the most current version of those files. So from your downloaded latest copy just overwrite both those locations.
There should be two files in the update folder, update.php and langs.zip Just overwrite the langs.zip in the update folder with the one in the plugin root.... The reason is that its possible that the dev updated the root langs.zip folder but forgot to copy it over to the update folder.
If that does not work then your stuck with creating the lang key values yourself using the
dev-tools process. Youll need to guess what the text should say and then add the lang key for that lang code using dev-tools. But remember you need to do the same as the dev should have when you are done adding... export the lang file and upload it to the root plugin folder and update folder
I hope this helps.... sorry you all have to deal with this from that dev that decided to just leave.
Sir - i tried adding the codes (it was missing) but nothing happened..
Now i am trying to do the 2nd step you mentions "First i would download the plugin from your plugins list, then i would take the langs.zip file from the root of the plugin download and stick it into the update folder and also overwrite the langs.zip file in the plugin root on the server as well. "
Can you please help with file path and steps how to do it...
Really thank you for giving such a relief to people and help us out!
Thanks by heart,
Look fw
Ashish
It sounds like the dev forgot to import the new language keys after he updated the plugin.
To spell this out here is the process that devs follow when updating the lang in a plugin.
If they have a new text variable, they create that variable in the language file using the dev-tools portion of admin section using this process
https://wiki.oxwall.com/faq:site_configuration:manage_languages?s[]=dev&s[]=tools
Then when the dev is done with that process they MUST remember to export their lang file for the plugin and then upload it to the server of their dev version and overwrite the langs.zip file. This will allow them to use the most current copy of the langs file on their dev copy.
They also need to remember to set the new import value for the new langs.zip file in the update folder of the update so that when a user updates they get the new lang.zip file imported to thier copy.
I suspect that the dev either forgot to include the lang.zip import command in their update folder file or they saved their dev copy without exporting the current lang.zip version and including it in their released copy.
Either way the solution is this:
1. open up the last update folder for the plugin and look inside the update.php file... there should be a command that looks like this:
OW::getLanguage()->importPluginLangs(OW::getPluginManager()->getPlugin('PLUGINNAME')->getRootDir().'update/NUMBER/langs.zip', 'PLUGINNAME');
PLUGINNAME is the name of your plugin... and the NUMBER is the number of the update folder... if the folder is named 7 then there should be a 7 for NUMBER
If that code is not in that file then add it... the plugin name should be in lowercase.
Make sure there is a langs.zip file in the update folder as well. If it is not there then you need to download a fresh copy of your plugin from the oxwall server and upload the langs.zip folder from the plugin root to the update folder.
Then uninstall the plugin and reinstall, clear your cache and you should now have the missing lang values.
If that code is there and it has the right number and plugin name, then that means that the dev forgot to update with the right copy of the langs.zip file... In this case the fix is somewhat longer....
First i would download the plugin from your plugins list, then i would take the langs.zip file from the root of the plugin download and stick it into the update folder and also overwrite the langs.zip file in the plugin root on the server as well.
To be cliear here, when an update is issued on a plugin the plugin root langs.zip file and the update folder (number of release) langs.zip file should be the most current version of those files. So from your downloaded latest copy just overwrite both those locations.
There should be two files in the update folder, update.php and langs.zip Just overwrite the langs.zip in the update folder with the one in the plugin root.... The reason is that its possible that the dev updated the root langs.zip folder but forgot to copy it over to the update folder.
If that does not work then your stuck with creating the lang key values yourself using the
dev-tools process. Youll need to guess what the text should say and then add the lang key for that lang code using dev-tools. But remember you need to do the same as the dev should have when you are done adding... export the lang file and upload it to the root plugin folder and update folder
I hope this helps.... sorry you all have to deal with this from that dev that decided to just leave.
ow_plugins/pluginname/ overwrite the langs.zip that is already there.
and
ow_plugins/pluginname/update/last update number/ also overwrite that file as well.
then clear your cache and you should have the latest values, the reason that you also copy it into the update folder is just in case you decide to rerun the update it will have the latest file...
But the big deal is to be sure you overwrite the root langs.zip file...
If you have downloaded the latest copy of the plugin, simply copy the langs.zip file from the download root to
ow_plugins/pluginname/ overwrite the langs.zip that is already there.
and
ow_plugins/pluginname/update/last update number/ also overwrite that file as well.
then clear your cache and you should have the latest values, the reason that you also copy it into the update folder is just in case you decide to rerun the update it will have the latest file...
But the big deal is to be sure you overwrite the root langs.zip file...
when i say download root folder im talking about when you open up the download plugin folder and the name of the plugin folder (that is the download root)
So basically youll have to try to see if the dev forgot to update the langs.zip file in the oxwall root ow_plugins/pluginname folder or not. So see which file is larger, the one in the download root or the one in the download /update/number whichever is larger is the one you want to add to the oxwall install ow_plugins/pluginname/
Now I am back and commited to provide support.
Apologies again.. Pleaset let me know if you have any issues and I will take it as priority.