constantin980

Adding a counter for tags that do not contain <div> or <h1>, and implementing a counter to limit the data retrieval for the short description, sounds like a practical solution to enhance control and efficiency in data management. For tags without <div> or <h1>, we can create a function to count them during the data retrieval process. This function will iterate through the tags and increment the counter for each tag that doesn't contain <div> or <h1>. This counter can then be displayed or used for further processing as needed. Similarly, for limiting the data retrieval for the short description, we can incorporate a counter that tracks the number of characters retrieved. This counter can be set to a specific limit, and the data retrieval process can be programmed to stop once the limit is reached. This will prevent excessive data retrieval and ensure that the short description remains within the desired character limit. By implementing these counters, we can introduce better control and optimization in data retrieval processes, leading to improved efficiency and performance. It is advisable to remove characters from tags containing <div>, <h1>, <h2>, etc., to ensure data integrity and uniformity. This will allow us to focus only on the text content within these tags and avoid including HTML code or other formatting elements in our data. By removing these characters, we will simplify the data processing process and ensure that the retrieved information is clean and relevant. This practice will improve the quality and consistency of our data and facilitate its use in various contexts and applications. Regarding the addition of the product ID to the error message, that sounds like a beneficial enhancement. It would certainly provide users with clearer feedback when they encounter errors related to exceeding character limits. Regarding the puzzling issue concerning the processing of records, I apologize for any confusion caused. Upon further investigation, it seems that the occurrence of records not being processed is an isolated incident. I haven't been able to reproduce it consistently, and it appears to happen sporadically. Unfortunately, I don't have specific details regarding whether it affects the first or last record, or if it's related to specific fields. I will keep monitoring the situation and provide more information if it recurs.

I'm reaching out to follow up on the recent tests conducted regarding the limitation of the "Description Short" field. Unfortunately, it seems that the issue persists, as instead of encountering a specific error message when the character limit is exceeded, users are only met with a generic error prompt. The description_short field is too long. The length is 960. The maximum allowed length is 800 on line 1. Upon reviewing the test results, it has become evident that a more informative error message would greatly enhance user experience. Specifically, when the character limit for the product ID is surpassed, it would be beneficial for users to receive a notification indicating that the character limit has been exceeded and that their input needs to be restricted accordingly. To address this issue effectively, I would recommend implementing an error message that explicitly states when the character limit for the product ID has been reached, prompting users to adjust their input accordingly. Additionally, upon acceptance, users should be made aware that their input has been limited to adhere to the specified character count. By incorporating these adjustments, we can ensure that users are provided with clear and actionable feedback, thus enhancing the usability of the system. Please let me know if you require any further clarification or if there are any additional steps we need to take to resolve this matter. Thank you for your attention to this issue. ps: Also, I have identified another limitation in operation that requires attention. When setting the number of records to 100 or 200 for bulk editing, it is observed that only 199 products are edited, with one product consistently remaining unchanged.

please keep in mind when copying these tags that they should not exceed 800 characters for the short description and 21844 characters for the long description, if they exceed these characters the products become unavailable

I've noticed that we need a bulk update for the description and tag copy fields in our system. Specifically, when we copy the tags into the description field, they should be concatenated with spaces between them. For example, if we have the tags "555444" and "12222", when copied into the description field, they should appear like this: "555444 12222", with a space between them. However, we've observed that currently, these tags are being copied without spaces between them. Please consider this request and update our procedures accordingly or identify the most suitable solution to implement this behavior. Thank you in advance for your attention to this request and for your efforts in implementing the necessary changes.

https://gitlab.com/cargus/cargus-modules/prestashop/-/releases ultima versiune actualizata acum 3 luni

Poate oferi cineva detalii???? Ma intereseaza si pe mine

Intri in Design, Pagini Iti crezi o categorie Exemplu Blog si cate subcategorii vrei tu si poti sa adaugi cate paginii vrei tu. Pana ce ai bani si iti cumperi un modul pentru Blog .

Eu am refacut magazinul de la zero ca sa il trec de la 1.6 la versiune 1.7.2.3, am muncit din nou aproximativ o luna sa introduc fiecare produs. Eu folosesc tema clasica cu mici modificari. Va recomand versiune 1.7. pentru ca se misca foarte bine , este mult mai usor de folosit , credeam ca o sa fiu penalizat de catre google dar dimpotriva paginele au ajuns pe primele pagini de cautare din primele zile de la indexarea sitemap. Nu vreau sa deschid un topic nou si incerc sa va adresez o intrebare aici. Am facut upgrade de la v1.7.2.3 la v.1.7.2.4 cu 1 click upgrade in 2 minute upgrade a fost gata ,am sters memoria cache si am regenerat imaginele totul mergea ok pana ce am deschis cpanel si la Physical Memory Usage aveam 350 din 600 la 2 vizitatori simultan . Inainte sa fac upgrade aveam Physical Memory Usage 122,7 din 600 la aproximativ 25-30 vizitaori simultan. Resurse Alocate: CPU 100% PHP-Mem 512MB MySQL 10 vMem 1GB pMem 600MB I/O 4MB/s nProc 30 EP 25 IOPS 1024 Vreau sa trec la urmatoarea versiune dar nu as vrea sa fie server overload de la un trafic mic sau sa achizitionez un pachet de resurese mai mari. Trebuie sa fac o optimizare si care ar fi aia sau sunt module care optimizeaza presta la fiecare upgrade???

sa iti zic eu cum am facut si am reusit dupa zeci de zile de cautari. am incarcat in public_html/admin_folder/autoupgrade/download arhiva copiata de pe site official prestashop_1.6.1.17 Am modificat numele la arhiva prestashop_1.6.1.17 cu prestashop_1.6.1.18 intri in Parametri avansati / 1-Click Upgrade Intri in Modul Expert alegi canalul Arhiva Locala si foloseste arhiva prestashop_1.6.1.18.zip pentru a actualiza la versiune 1.6.1.18 Salvezi si faci Upgrade. Hopa problema persista asa ca am incercat si fara Certificat SSL si functioneza perfect daca folosesti un Certificat SSL incearca prima data sa intri in admin fara el si incearca sa vezi daca problema persista. Trimite un raspuns daca te-a ajutat cumva.

Aceiasi problema o am si eu. Failed to load resource: the server responded with a status of 508 () /100/index.php?controller=AdminProducts&token=5978b555c7bd55f9a7a38e5e6009b8b3&id_product=27&action=Customization&updateproduct&ajax=1&rand=1508254955863&_=1508254953795 Failed to load resource: the server responded with a status of 508 () products.js:177 Uncaught TypeError: Cannot read property 'replace' of undefined at Object.<anonymous> (products.js:177) at j (jquery-1.11.0.min.js:2) at Object.fireWith (jquery-1.11.0.min.js:2) at x (jquery-1.11.0.min.js:4) at XMLHttpRequest.b (jquery-1.11.0.min.js:4) products.js:177 Uncaught TypeError: Cannot read property 'replace' of undefined at Object.<anonymous> (products.js:177) at j (jquery-1.11.0.min.js:2) at Object.fireWith (jquery-1.11.0.min.js:2) at x (jquery-1.11.0.min.js:4) at XMLHttpRequest.b (jquery-1.11.0.min.js:4) /100/index.php?controller=AdminProducts&token=5978b555c7bd55f9a7a38e5e6009b8b3&id_product=27&action=Attachments&updateproduct&ajax=1&rand=1508254955873&_=1508254953796 Failed to load resource: the server responded with a status of 508 () /100/index.php?controller=AdminProducts&token=5978b555c7bd55f9a7a38e5e6009b8b3&id_product=27&action=Suppliers&updateproduct&ajax=1&rand=1508254955900&_=1508254953797 Failed to load resource: the server responded with a status of 508 () products.js:177 Uncaught TypeError: Cannot read property 'replace' of undefined at Object.<anonymous> (products.js:177) at j (jquery-1.11.0.min.js:2) at Object.fireWith (jquery-1.11.0.min.js:2) at x (jquery-1.11.0.min.js:4) at XMLHttpRequest.b (jquery-1.11.0.min.js:4) products.js:177 Uncaught TypeError: Cannot read property 'replace' of undefined at Object.<anonymous> (products.js:177) at j (jquery-1.11.0.min.js:2) at Object.fireWith (jquery-1.11.0.min.js:2) at x (jquery-1.11.0.min.js:4) at XMLHttpRequest.b (jquery-1.11.0.min.js:4) /100/index.php?controller=AdminProducts&token=5978b555c7bd55f9a7a38e5e6009b8b3&id_product=27&action=Warehouses&updateproduct&ajax=1&rand=1508254955942&_=1508254953798 Failed to load resource: the server responded with a status of 508 () products.js:177 Uncaught TypeError: Cannot read property 'replace' of undefined at Object.<anonymous> (products.js:177) at j (jquery-1.11.0.min.js:2) at Object.fireWith (jquery-1.11.0.min.js:2) at x (jquery-1.11.0.min.js:4) at XMLHttpRequest.b (jquery-1.11.0.min.js:4) /100/index.php?controller=AdminProducts&token=5978b555c7bd55f9a7a38e5e6009b8b3&id_product=27&action=Prices&updateproduct&ajax=1&rand=1508254955653&_=1508254953786 Failed to load resource: the server responded with a status of 404 () products.js:177 Uncaught TypeError: Cannot read property 'replace' of undefined at Object.<anonymous> (products.js:177) at j (jquery-1.11.0.min.js:2) at Object.fireWith (jquery-1.11.0.min.js:2) at x (jquery-1.11.0.min.js:4) at XMLHttpRequest.b (jquery-1.11.0.min.js:4)

http://store.nemops.com/free-modules/43-carrier-assigner-free-module.html#.WSHTU5KGPIV Am rezolvat

Am activ advanced stock management . Folosesc Casn on delivery (COD) v.1.0.0- de Prestashop Nu vreau sa taxez suplimentar clientul final , vreau sa fie ajutat sa primeasca produsul la un pret care merita nu suprataxat. Credeam ca pot sa adaug un cod suplimentare genul "if" este selectat DHL sa nu mai apara Plata COD. Macar sa pot sa notific clientul in Front Office in ce depozit se afla produsul in dreptul "Add to cart" ar fi bine si atat .

Buna ziua . Sper sa ma exprim corect. Am configurate doua depozite in Prestashop 1.6.1.11 primul se afla in UK si al 2 in Iasi . Transportatori folosesc 3 , Posta Romana care ofer transport Gratuit , Urgent cargus si DHL cu plata. Pentru depozit din Iasi folosesc Posta Romana si Urgent Cargus. Pentru depozit din UK folosesc DHL.Cam scumpi dar livreaza in 3 zile lucratoare Rugamintea mea este sa ma ajutati sa setez platile pentru fiecare depozit in parte . Pentru depozit din UK plata cu card, paypal si transfer bancar dar fara plata Ramburs (mam trezit cu comenzi fantoma la adrese care nu exista nimeni) Pentru depozit din Iasi vreau sa folosesc plata cu card, paypal , transfer bancar plus plata Ramburs (pierd mai putini bani daca nu isi ridica marfa care o expediez din Iasi. INTREBAREA MEA ESTE , Cum pot scoate plata ramburs pentru produsele din depozit din UK in schimb sa pastrez pentru cele din depozit din Iasi? Va multumesc anticipat