http___www.vbenterprisetranslator.com_forum_ga_archive_t-245.html_1.xml
1.1 2.1 2.2 3.1 4.1 5.1 6.1 7.1 8.1 9.1 10.1 11.1 12.1 14.1 15.1 15.2 15.3 15.4 16.1 17.1 17.2 18.1 18.2 19.1 19.2 20.1 20.2 20.3 21.1 23.1 24.1 24.2 25.1 26.1 27.1 27.2 27.3 28.1 29.1 30.1 31.1 32.1 33.1 35.1 36.1 38.1 38.2 39.1 39.2 40.1 41.1 42.1 43.1 43.2 44.1 45.1 46.1 46.2 47.1 48.1 51.1 51.2 51.3 51.4 52.1 52.2 53.1 53.2 53.3 54.1 54.2 55.1 56.1 57.1 58.1 58.2 59.1 61.1 63.1 63.2 64.1 65.1 65.2 66.1 67.1 68.1 69.1 70.1 71.1 72.1 73.1 74.1 74.2 75.1 77.1 77.2 77.3 77.4 77.5 78.1 78.2 79.1 81.1 81.2 82.1 83.1 83.2 84.1 85.1 86.1 87.1 88.1 89.1 89.2 90.1 90.2 91.1 91.2 92.1 92.2 92.3 93.1 93.2 93.3 94.1 95.1 95.2 95.3 95.4 96.1 96.2 96.3 96.4 97.1 97.2 97.3 98.1 98.2 99.1 100.1 101.1 102.1 103.1 105.1 106.1 107.1 107.2 108.1 108.2 108.3 109.1 109.2 110.1 110.2 111.1 111.2 112.1
View Full Version : Solved Additional langtitle parsing issue Using vbSEO. Screenshot attached. http://www.pentaxforums.com/forums/members/adam-albums-website-news-screenshots-picture5413-a.gif I will find a fix for this in the vBSEO function that handles this. In functions_vbseo_vb.php: find vbseo_thread_seotitle($getnextoldest); replace vbseo_thread_seotitle($getnextoldest); if (strpos($getnextoldest['title'], '[/langtitle]')) { require_once('vbenterprisetranslator_functions_bbcode.php'); $getnextoldest['title'] = vbet_parseTitle($getnextoldest['title']); $vbseo_gcache['thread'][$getnextoldest['threadid']] = $getnextoldest; This should be not necessary. Did you integrated vBET with vBSEO like it is described in readme.html file? Which version of vBET are you using? Last one have global langtitle parsing functionality. Yes and I'm using the latest version, 3.3.3. Strange. Please tell us how to reproduce the issue - we will work on more elegant solution which will not require additional vBSEO files change. Can you reproduce it on out server? I.e. in test messages area? No, this cannot be demonstrated here, because you don't use the vBSEO option to include thread titles in next/previous links (those shown directly below the quick reply editor). You'd first need to enable the option. OK so - we know now how to reproduce it. We will check it on our test instance and seek for other solution. Great thanks! kamilkurczak Sorry, but we can't reproduce this problem. We tested it on 3.5.0 vBSEO and 3.3.3 vBET. Which versions do you have? Please make sure you have installed the latest version vbet (if you used it) what about update product_vbenterprisetranslator.xml from do-not-upload folder? I'm using vBET 3.3.3 and vBSEO 3.3.2. My langtitle tags aren't being parsed in the profile statistics page either now, it seems. Quite strange! To fix the parsing of langtitle under the profile "statistics" tab (where it says "last post: ..."), I made this change in class_userprofile.php: Find: $this->prepared['lastposttitle'] = $getlastpost['title']; Replace: $this->prepared['lastposttitle'] = $getlastpost['title']; if (strpos($this->prepared['lastposttitle'], '[/langtitle]')) require_once('vbenterprisetranslator_functions_bbcode.php'); $this->prepared['lastposttitle'] = vbet_parseTitle($this->prepared['lastposttitle']); There's no way the tags are being globally parsed, as otherwise this change wouldn't be needed. There are also no hooks in that class file. Please PM access details to FTP, Admin CP and vBSEO CP. Since we are not able to reproduce it on our side we have to check it on our server. Please undo your changes before you give us access details (we need to see the issue to diagnose it) - you can made copies of files to easily bring it back again. As I wrote vBET 3.3.3 should parse langtitle globally, at this moment I'm not able to tell does it is some bug, conflict with other plugin, or wrong vBET update. I'm traveling abroad this week, and will not be available to handle any backend website issues apart from those posted here on the forum. Could you show me where in the code the tag is globally parsed? I can then take a look and let you know if I can see why it's missing certain areas. open file: /includes/vbenterprisetranslator_functions_hooks.php and look for vbet_global_complete there is used function vbet_parseTitleGlobally (from /includes/vbenterprisetranslator_functions_bbcode.php) Thanks! I will investigate this. I've found a few more in the navbits on inlinemod.php and postings.php. Can you reproduce this behavior on this site, i.e. when editing a translated thread? During edition it is OK to leave it. You need to see original text to be able to edit it. That is why parsing is disabled on edition page. It should work this way and it is harmful - Google and other visitors see approved text, not during edition :) Does the issue still exists? What it the status? We are preparing for new release and want to solve all issues. If you found that it was some conflict - please confirm. If you cannot handle it - please PM access details, so we will be able to check it and in case of bug include solution in next release. I've added the parsing manually to the locations listed in this thread. There are no more visible parsing problems. Nevermind- found another: translated PM titles aren't parsed in the page titles on private.php Fixed by adding a plugin at private_complete: if (strpos($pagetitle, '[/langtitle]')) { require_once(DIR. '/includes/vbenterprisetranslator_functions_bbcode.php'); $pagetitle = vbet_parseTitle($pagetitle); And another: I couldn't find a way to fix this via plugins. Instead, I added this code to usercp.php: if (strpos($reputation['title'], '[/langtitle]')) { require_once(DIR. '/includes/vbenterprisetranslator_functions_bbcode.php'); $reputation['title'] = vbet_parseTitle($reputation['title']); } Directly below $reputation['timeline'] = vbdate($vbulletin->options['timeformat'], $reputation['dateline']); $reputation['dateline'] = vbdate($vbulletin->options['dateformat'], $reputation['dateline']); $reputation['reason'] = $bbcode_parser->parse($reputation['reason']); Nevermind- found another: translated PM titles aren't parsed in the page titles on private.php Fixed by adding a plugin at private_complete: if (strpos($pagetitle, '[/langtitle]')) { require_once(DIR. '/includes/vbenterprisetranslator_functions_bbcode.php'); $pagetitle = vbet_parseTitle($pagetitle); I really cannot reproduce this issue on our server. I suspect that you do not have installed appropriately vBET 3.3.3 - please check it. We had many times issue that our clients just uploaded new files and forgot to import new product file or the opposite. Did you checked does execution of function vbet_global_complete exist in described place? (http://www.vbenterprisetranslator.com/forum/bug-reporting/702-additional-langtitle-parsing-issue-2.html#post3137) Also we are running our forums now on vBET 3.3.4 beta version, so it can be that bug exist in 3.3.3 and we already fixed it (do not remember that). Still -please confirm that your actual installation is OK - best made update to 3.3.3 again. And another: I couldn't find a way to fix this via plugins. Instead, I added this code to usercp.php: if (strpos($reputation['title'], '[/langtitle]')) { require_once(DIR. '/includes/vbenterprisetranslator_functions_bbcode.php'); $reputation['title'] = vbet_parseTitle($reputation['title']); } Directly below $reputation['timeline'] = vbdate($vbulletin->options['timeformat'], $reputation['dateline']); $reputation['dateline'] = vbdate($vbulletin->options['dateformat'], $reputation['dateline']); $reputation['reason'] = $bbcode_parser->parse($reputation['reason']); If this page is using global_complete hook then it should be handled in vBET 3.3.3 - please see previous response about that. If global_complete is not used - then such file change will be necessary or you can add it to some hook if there exist some on this page. My product file and all the PHP files are showing up as v3.3.3, as they should be. However, I have modified many files and have quite a few plugins installed on my forum, so it's somewhat likely that there may be a conflict. I've noticed that the execution time on the global_complete hook is 1000. Shouldn't this be higher to avoid conflicting with other plugins? I've confirmed the presence of the global parsing function. I very carefully upgraded to 3.3.3, so I doubt that file contents can be an issue here. However, I see no further bugs, so I think I'm good for the time-being. I'm also happy to say that vBET's performance hit on my server is negligible, so I may not be upgrading past 3.3.3 due to the high number of customizations/working fixes I've implemented on my own. With 800 online, I've had server loads below 1.00, and with 1,200 online, they were around 3.00. Not bad for a dual hex-core Xeon server, I think! I think too! So - getting back to the issue. vBET should handle automatically those cut langtitle (with ...) - we are not able to reproduce it on our forums and want to made new release soon. It would be great if we could find the reason of this and fix it if it is on our side. If you can PM access detail to your forum, or even your test instance where those things happen we could to that - we could fix it :) At this moment without possibility to reproduce we even cannot be sure does it is really vBET bug (not some conflict with other mod or configuration issue). So we are in dead point now in this area. Once again - we would gladly solve this issue on your side if you will. There is possibility that new vBET release will be this weekend - would be great to close all issues before :) I found that we really had a bug there. Global langtitle parsing was inside of unnecessary condition so it not always was evaluated. This is already corrected and will be included in next release. Could you please post a quick fix for that? I can't upgrade to 3.3.4 right now :( I'm guessing that the unnecessary condition is the one below: function vbet_parseTitleGlobally(&$title, $removeNotTranslateSection = false) { if ($_GET['do'] != 'postthread' && $_GET['do'] != 'comment' && 0!==strpos($_GET['do'], 'edit') && 0!==strpos($_GET['do'], 'update') && strpos($title, '[langtitle=')) { return vbet_parseTitleMultiple($title, $removeNotTranslateSection); What hold you with update? I will look in out SVN to check what changes was made to solve the issue, but still - you will need last release first to be able to made quick fix if we publish it. I've made several modifications to the code over time, and I've forgotten where and why. I don't want to be breaking things that already work! Please note that we are not responsible for code changed by our clients - we are simple not able to do that. If your changes was according to our quick fixes then you can be calm - those will be included in next release so everything will be OK. If you made some other code changes, then we advice to write some document which will guide you about your personal additional steps during updates - otherwise you will stay with old vBET version, because you o not know what and what for you changed. Please note that I found what changes are necessary to solve this issue, but I cannot publish quik fix on forum (because it includes broken bbcode inside). So pelase ask about it by email (contact@vbenterprisetranslator.com) and I will send it to you there. I agree- life would be easier if I had documented the changes. As far as I recall, they were all bug fixes, and not new features, etc. E-mail sent! Thanks! Powered by vBulletin® Version 4.2.2 Copyright © 2015 vBulletin Solutions, Inc. All rights reserved.
1.1 2.1 2.2 2.3 2.4 3.1 4.1 4.2 4.3 5.1 6.1 6.2 7.1 7.2 7.3 8.1 9.1 10.1 12.1 13.1 13.2 14.1 15.1 16.1 17.1 19.1 20.1 21.1 21.2 22.1 22.2 23.1 23.2 23.3 24.1 25.1 25.2 25.3 26.1 27.1 28.1 28.2 29.1
View Full Version: Tacaíocht do CMPS vBadvanced Dia duit, bheadh sé iontach dá mbeadh CMPS vBadvanced tacú leis. Tá an tairseach suite ar an index.php, lasc mé an teanga ar fud anseo, ansin talún mé an leathanach Baile Fóram (i mo forum.php). Mar sin, mé a fháil ar an leathanach tairseach atá le haistriú. Go raibh maith agat agus Maidir, Crochadóir Dia duit, táimid ag pleanáil chun tacú le mods is mó tóir ar a mbeidh gá le comhtháthú speisialta. Ag an nóiméad seo ní mór dúinn a lán oibre ar leagan 3.3.0. Tar éis go mbeidh a rinne muid comhtháthú le foinse cumhachta 4.0 agus ansin beidh muid a chur ar ár n-aird ar mods eile. Fós tá muid réidh-am ar fad chun tacú le húdair mod a bheadh buíochas a integrations a rinne iad féin, ag freagairt dóibh a cód bhfuil gá agus nuair ba chóir é a chur. Conas is féidir liom a dhéanamh chun a pharsáil leathanaigh langtitle vbcmps. ps. Is é seo an snáithe leanúint ar ardaíodh san ábhar seo: Tá áthas orm go kontynować tú é anseo :) Tríd is tríd, tá tú a fháil áit ina Leagann mod an luach na teidil, a taispeántais ansin, agus ansin cuir an píosa seo a leanas de chód ann (uaireanta caithfidh tú a mhodhnú go fóill - anseo go bhfuil siad sásta chun cabhrú le duine éigin i láthair cheana féin faoi uisce cód). Is Dul isteach cód breise go díreach sa chód an faisean simplí, cé nach gá an chuid is fearr. Cód Samplach a bheith san áireamh (ní mór duit a athrú ar an ainm an athróg a ionadaíonn do na $ teideal teideal): if (strpos($title, '[/langtitle]')) { require_once(DIR. '/includes/vbenterprisetranslator_functions_bbcode.php'); $title = vbet_parseTitle($title); Mar a d'fhéadfadh de dhíth orm le hathrú saorga an gcód - i gcás má tá an teideal gearrtha ansin, ach is féidir liom a thaispeáint ar an gcód i bhfaca cé tú féin zanużyć amháin. Rinne mé: D Díreach mar a scríobh tú go raibh sé riachtanach a mhodhnú an cód le beagán. Bhí an abairt $ teideal a athrú chun $ snáithe [teideal] i gcomhréir 253 sa recentthreads.php comhad (fréamh Fóram / modúil /) chuir mé an cód seo a leanas: // Langtitle if (strpos($thread['title'], '[/langtitle]')) { require_once(DIR. '/includes/vbenterprisetranslator_functions_bbcode.php'); $thread['title'] = vbet_parseTitle($thread['title']); Tá sé beagnach gach rud. : Cool: Tá mé fadhb beag amháin leis sin. : P Más rud é mo fóram Polainne "Ábhair Déanaí" ábhar scríofa i Rúisis, ag athrú an teanga a Rúisis, fuair mé leathanach bán bán. (Teangacha eile ag obair fíneáil.) Tá mé fadhb beag leis sin. : P Is chás go bhfuil mo fóram Polainne sa "Topaicí le déanaí" a scríobh faoi na Rúise, ag athrú an teanga a Rúisis, fuair mé leathanach bán bán. (Obair Teangacha eile fíneáil.) Agus má tá aon eolas inár logáil isteach bhfreastalaí? Cuir Podeślij nasc cruinn ar an leathanach leis an "Ábhair le déanaí" agus scríobh ar cad é go díreach Cliceáil chun amharc ar an leathanach bán. Agus má tá aon eolas inár logáil isteach bhfreastalaí? Cuir Podeślij nasc cruinn ar an leathanach leis an "Ábhair le déanaí" agus scríobh ar cad é go díreach Cliceáil chun amharc ar an leathanach bán. Iompaigh sé amach go bhfuil an chuma leathanach bán ach amháin ar mo fianáin FireFox .... ;) Ach tá fadhb agam. Tar éis a chur leis an cód roimh an t-ainm dealraitheach a thuilleadh dom an teachtaireacht: [langtitle = Tá brón orm a athrú ar an teanga, na téamaí scríofa i dteanga iasachta nach bhfuil aistrithe agus tá siad fós sa Pholainnis. Iar scríofa ar dtús i Rúisis: "BoзbMиTe B лиry" araon sa teanga Polainnis, Rúisis agus aon vbcmps leathanach eile ar taispeáint mar: "Tóg i léig" http://fifa.pes.com.pl/ Réitithe. Go dtí amaideach a ligean isteach, ach úsáid mé vB a bharrfheabhsú agus is dócha ní raibh athnuachan an taisce agus dá bhrí sin na fadhbanna seo. Go raibh maith agat as an réiteach. :) Automatic Translations (Powered by Google, Microsoft®, Yandex , SDL Language Cloud and Apertium): Powered by vBulletin® Version 4.2.2 Copyright © 2015 vBulletin Solutions, Inc. All rights reserved. SEO by vBSEO