Jump to content

Fredi

Members
  • Content count

    506
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by Fredi

  1. Fredi

    The Unit conversion

    For stores selling goods to different countries, this option will be useful. It will be good if this option is associated with the buyer's country, for example, through the tables in the database - coustomers or address_book or address_format, or zones. The client can choose the parameters of weight and dimensions when creating an account or placing an order. There should be an option to change these parameters when completing the checkout. Why? A customer from England can place an order for his beloved girl who lives in France, and the seller's store is located in California.
  2. Fredi

    Translations

    I tested your version a little and saw that not all text constants are translated in the Admin. Hopefully everything will be in order in the final release.
  3. Fredi

    Translations

    Russian language - no problem. Continuous support and updates.
  4. Fredi

    New management and osCommerce v4

    Good news. I have been expecting this news for a long time.
  5. Fredi

    AJAX Attribute Manager support

    Hello @raiwa, New updated russian file for AJAX Attribute Manager v3.3.5 attributeManager.zip
  6. Fredi

    BREXIT: shopowners in the UK

    Do I need to add a new currency to the store or is it acceptable to use Euro for the UK? Need to set the currency - pound sterling? We have not had buyers from this country for a long time.
  7. OsCommers was created and continues to work as a universal international platform for Internet commerce. Phoenix turns into a local marketplace for 1 country. Do you want to trade internationally? ORDER CODE FROM PROFESSIONAL. Well then. Let's wait for the announced news.
  8. Fredi

    AJAX Attribute Manager support

    I installed everything. Problem with modifying products_attributes.php file in Options Images BS v1.6.1 by Tsimi module. This file is very old and does not match the modern modified Admin kernel. This is the only problem. It needs a lot of changes to add the attribute images. Everything is much easier with the weight option. There are few changes to your module.
  9. Fredi

    AJAX Attribute Manager support

    Ok, Rainer. The error I'm having is related to trying to add attribute images to your module. If I install your module unchanged, it works great ! 👍
  10. Fredi

    AJAX Attribute Manager support

    Thank you very much for your answer, Rainer! Weight option is highly desirable in our store. Some product attributes are weighted and change the total weight of the order. Therefore, the weight adjustment option will be a useful option for stores. Such an example: we for example sell a valves for irrigation systems. This valve has the same structure but different weight. If we use a product attribute such as diameter, for example 1/2 ", 3/4", 1.0 ", 1 1/4", 1.5 ", 2", the weight of the item is very different. There are two options: place 6 products on the site, or place 1 product, but with 6 attributes. Picture options are also very convenient to work with. For example, drippers for irrigation have a water flow rate of 0.8, 1.2, 2.0, 4.0 liters per hour. They have the same design and differ in color. They have a very small difference in weight, but when a customer orders 100 or 1000 pieces, the weight option also matters. I think if we can modify the module using these two options, we will get a fully functional module that will be useful for many stores.
  11. Fredi

    AJAX Attribute Manager support

    Hello dear Rainer. Please tell me if there is a solution to the question I asked?
  12. Fredi

    Article Manager v1.0

    Thanks a lot for answering Jack. I know these guys won't give an answer. They have such a principle. Harald's updates required a lot of work, but were very simple. Updating in connection with the transition to the SSL was also not very difficult. Updates related to changes in the PHP version were also not very difficult. Most of the users did all these updates themselves. Order from professional coders. It is possible, but if you need 1-2 modules. When you need to update an old, large, multifunctional store in which there are many modules, everyone refuses such work. I made applications to almost all the leading coders of OsCommers, but everyone refused my order. I have kept the applications and answers to them in my archive. The main answer is "sorry, I have a lot of work and I don't have time to deal with your store ..." The problem is big. Today's concept - a stable breaking of the kernel code once a month, creates additional problems. Which coder would dare to adapt an existing store for a phoenix? What guarantees can the encoder give to the customer? Nothing wrong. Life is a difficult and difficult path. We will go forward, even if there are artificial obstacles on the way.
  13. Fredi

    Jssor Slider

    Thank You Jack! Installed the module on a test site, everything works SUPER!👍👌
  14. Fredi

    Article Manager v1.0

    Unfortunately I have not received a response from the Phoenix CORE CODERS. What reason? Don't you have an answer? Do you know how to do this? Or does OpenSource not provide information about the code, its structure and the concept of specific software? Thank you very much dear coders.
  15. Fredi

    AJAX Attribute Manager support

    Hello Rainer! I've been using your wonderful module for many years now, but at OsCommers. Installed the latest version on my Phoenix test store 1.0.7.10 When I enter it, there is a warning:Notice: Undefined offset: 222 in /admin/attributeManager/classes/attributeManager.class.php on line 237Notice: Undefined offset: 229 in /admin/attributeManager/classes/attributeManager.class.php on line 237 In the old store I also use the weight and attribute images add-ons. These 2 additions have not been updated for many years and do not correspond to modern PCP versions. Special issue with "Attribute Image" that requires a big change to the products_attributes.php file I tried it, but not everything worked out. File \admin\attributeManager\languages\russian\attributeManager.php has an unreadable format (encoding does not correspond to UTF-8). I fixed that, new translation in the attached file. Please replace it in your Attribute Manager. Thank you for your wonderful and easy-to-use addon. I really want it to work correctly in Phoenix. attributeManager.zip
  16. Hello Matt.

    Please look at this message and if possible, please give an answer. This module is very important to me. Without an article manager, my store is useless and can't work.
    You are a great coder. You do everything at a high level. But for the kernel code you wrote to work successfully, you need the ability to adapt a large number of modules. Please help me figure out how to adapt complex modules for Phoenix. This will help not only me, but also many Phoenix users.

    Thank you for your great creative work and for the code you wrote.

     

  17. Fredi

    Article Manager v1.0

    Thank You Jack. The problems of adapting Article Manager to Phoenix does not give me the opportunity to transfer my existing stores to the Phoenix platform. A wise marketing policy for promoting Phoenix - prohibiting access to information about Phoenix, hinders the possibility of using Phoenix as real software for actually operating stores. The history of constant changes to the "UNCHANGEABLE" kernel code, in each new version breaks old modules that have been working in OSC for more than 10-15 years. The "STABLE" kernel code is constantly hard-coded. This has been going on for over a year. Recent corrections have seriously changed the template system. The idea is good. @ecartz a talented coder and he almost completely rewrote Phoenix in a new, modern style of programming. It's fine. But don't forget that thousands of stores continue to run on old code that is outdated. But there are thousands of modules written before. These modules need to be updated. This is difficult for a simple reason: the concept of changing the structure of the Phoenix code is not available. The principle of building templates is not available. The article manager needs to be adapted to the new template system. This is a complex process because the module includes many functions and pages. It is very difficult to do this without a clear understanding of the concept of building the new Phoenix templating system. New features applied: $group /// $module_key /// public function getContent($group) /// How to adapt this for the Article Manager? What files do you need to create? Where to place them? Hooks? includes/function/, Or /versioned/ Or elsewhere? Needed files? database_articles_builder.php cart_articles_builder.php cart_topics_builder.php cart_authors_builder.php I hope @ecartz will help and tell you about the correct application of the new functions and the template building system.
  18. Fredi

    Article Manager v1.0

    Hello Jack! I am testing for version 1.0.7.10 Made minor changes for compatibility with the standard Phoenix CEO schema. I'm using the TinyMCE Hook. The administration's side was almost completely corrected. There are problems with displaying topics and articles on the site page. This is due to the new Phoenix template system, which you have to figure out on your own. Information on the template building scheme for serious modules, such as the Article Manager, is not freely available. I'm not allowed into the Phoenix Club. Therefore, you have to do everything yourself. I'm not sure if I will succeed, but I am trying to do it. The reason I'm doing all this is because your latest version only works correctly in English. My attempt to add transcoding to UTF8, for example, to correctly display the short description of articles, was unsuccessful. Jack, you did a great job. Thank you so much. But some things I need to work differently. Therefore, at my primitive level, I try to do it. Working on the Article Manager forced me to study the Core Code in depth and in detail in order to understand how to work further. The kernel is really well written and smart. But its main feature is the impossibility of using thousands of old modules created by the community for the OSC. Unfortunately, this problem remains. 2-3 people from the old development team are still in the Club and are doing work to adapt old modules. It's good. But you and I are no longer in the club. We are denied access to information about Phoenix. Therefore, you have to dig into the code on your own and intuitively guess what tricks of the code the guys keep secret. If I am able to adapt the Article Manager to the new standard kernel code, I will report it.
  19. Fredi

    Article Manager v1.0

    I am trying to adapt Article Manager to the latest version of Phoenix. Unfortunately, your latest version doesn't work very well. I continue to experiment.
  20. Fredi

    Article Manager v1.0

    Sorry, Language constant echo TEXT_BY_AM . ' ' . '<a href="' . tep_href_link('articles.php', 'authors_id=' . $articles_listing['authors_id']) . '"> ' . $articles_listing['authors_name'] . '</a>'; Work no correct. I change code to: echo '<span class="article-line-caption">' . TEXT_BY_AM . '</span>' . '<a href="' . tep_href_link('articles.php', 'authors_id=' . $articles_listing['authors_id']) . '"> ' . $articles_listing['authors_name'] . '</a>'; add span class. /includes/modules/article_manager/article_listing.php line 24.
  21. Fredi

    Article Manager v1.0

    Fixed. article_listing.php <?php echo '<a class="main" href="' . tep_href_link($page, 'articles_id=' . $articles_listing['articles_id']) . '"><b>' . $articles_listing['articles_name'] . '</b></a> '; if (DISPLAY_AUTHOR_ARTICLE_LISTING == 'true' && tep_not_null($articles_listing['authors_name'])) { echo TEXT_BY_AM . ' ' . '<a href="' . tep_href_link('articles.php', 'authors_id=' . $articles_listing['authors_id']) . '"> ' . $articles_listing['authors_name'] . '</a>'; } ?> to - <?php echo '<a class="main" href="' . tep_href_link($page, 'articles_id=' . $articles_listing['articles_id']) . '"><b>' . $articles_listing['articles_name'] . '</b></a> '; if (DISPLAY_AUTHOR_ARTICLE_LISTING == 'true' && tep_not_null($articles_listing['authors_name'])) { echo '<span class="article-line-caption">' . TEXT_BY_AM . '</span>' . '<a href="' . tep_href_link('articles.php', 'authors_id=' . $articles_listing['authors_id']) . '"> ' . $articles_listing['authors_name'] . '</a>'; } ?>
  22. Fredi

    Article Manager v1.0

    uploads Your file:
  23. Fredi

    Article Manager v1.0

    Thanks Jack, I'll check it out now.
  24. Fredi

    Article Manager v1.0

    Problem in artile_listing : Warning: DOMDocument::loadHTML() expects parameter 2 to be int, string given in /includes/functions/articles.php on line 322 function tep_get_topic_seo_title($topic_id, $language_id) { $topic_query = tep_db_query("SELECT topics_seo_title FROM topics_description WHERE topics_id = " . (int)$topic_id . " AND language_id = " . (int)$language_id); $topic = tep_db_fetch_array($topic_query); return $topic['topics_seo_title']; } -- line -322 -- function tep_get_author_seo_description($author_id, $language_id) { $author_query = tep_db_query("SELECT authors_seo_description FROM authors_info WHERE authors_id = " . (int)$author_id . " AND languages_id = " . (int)$language_id); $author = tep_db_fetch_array($author_query); return $author['authors_seo_description']; } Notice: Trying to get property 'nodeValue' of non-object in /includes/functions/articles.php on line 338 function tep_get_articles_seo_description($article_id, $language_id = 0) { global $languages_id; -- line 338 -- if ($language_id == 0) $language_id = $languages_id; $article_query = tep_db_query("SELECT articles_seo_description FROM articles_description WHERE articles_id = " . (int)$article_id . " AND language_id = " . (int)$language_id); $article = tep_db_fetch_array($article_query); return $article['articles_seo_description']; } Both errors indicate blank lines of code.
  25. Fredi

    Article Manager v1.0

    It is just a common function to add bolding as needed. I think adding bold where necessary is very simple: <b> ____ </b> or <strong> ____ </strong> The use of BoldTag significantly complicates and makes the code heavier, adds an additional function and instead of a tag, we must write in the code: . $boldTags['start'] . ____ . $boldTags['stop'] . very simple: <b> ____ </b> or <strong> ____ </strong> I beg your pardon, I'm probably wrong, but for me every complication of the code is a problem. I am not a coder.
×