Mass mailing links changed - odoo-11

I have a problem with the links inserted in my mass mailing on Odoo 11 Community.
The links that should point to external sites are modified and point to my Odoo domain.
For exemple, https://github.com/odoo is changed to https://my-odoo-domain.com/odoo
But when I use the test button, links are good.
Any suggestions?

I solved the problem.
It was due to the absence of the link.tracker sequence which disappeared after the migration of the database.
I recreated it and it works again.

Related

Joomla1.5→3.9: Old Artisteer template breaks at a certain variable

I'm migrating a site from joomla 1.5 to 3.9. This is also my first time ever touching Joomla, so I'm on bare grounds.
So far, I've managed to install joomla with a fresh install, and template is almost there. We're planning on moving the data manually, since the database is filled with weird stuff from past hacks. Customer wants the template to be as it is, so no new visual things has to be changed.
Whenever I want to view an article, the whole thing crashes.
I have pasted the entire code from /html/com_content/article/default.php onto https://pastebin.com/Lr6padqf.
The site breaks at $canEdit on line 5.
I've searched far and wide, and can't find any solid solution.
Thanks in advance.
Did changes here and there, and only solved things "partially".
Solution was to delete the com_content folder, which is inside the html folder of the template.
This solution is apparently found everywhere if one googles right. :V

Changes in RPD not showing up in OBIEE

My question is this. I am using OBIEE 12c and recently I changed the .rpd file in offline mode and then uploaded it to the server. However I dont see my changes there.
Interesting is the fact that when I open the .rpd in online mode in Admin tool, which shows the current rpd in OBIEE, I see my changes. I tried editing in online or offline modes, changed the names of rpds, restarted the server, but nothing helped. What could be the reason?
EDIT.. It was my fault partially. I was making changes in BMM layer and I was pretty sure that my changes will be automatically updated in Presentation layer(it was when I checked with several aggregations), however in this case, my changes did not reflected in Presentation layer. Why is like this?
P.S. I was modifying hierarchies if important

Joomla 2.5.16 take up to 2min to load

A relative asked me to fixed a Joomla website (v2.5.16) who has been hacked last year, probably due to lack of update (is up to date now), unfortunately I have no information about this. The issue is that the front end take 2~ min to load. The administration is loading normally so whatever the issue is, it depend of the front end. I already disabled all modules one by one and switched the template with another one to make sure that thebug is not in template or plugins folders, without success.
I must add that the problem is "probably" more recent than the hack, according to this person. So maybe there was a script somewhere reaching a random server which may not work anymore.
PS : the website is on a shared hosting. I have the FTP access but no ssh.
I know that I don't give any details which can lead to resolve this, but I need more a method to track what can go wrong and where than a solution.
Thanks in advance,
We have written a lengthy post explaining why a website might be slow: http://www.itoctopus.com/20-questions-you-should-be-asking-yourself-if-your-joomla-website-is-slow
From the looks of it, it might that the website is still hacked. Try overwriting the Joomla files with a fresh Joomla install and see if that addresses the problem.
Solving this issue will probably involve some or all of the following:
updating Joomla and all third party extensions to the latest versions
checking for and fixing malicious files using http://myjoomla.com or
https://sucuri.net or similar
analysing the performance of the website using http://gtmetrix.com
(it's free) or similar to pinpoint and fix what is taking the most time to
load
If the website has been hacked, you may need to reset passwords etc once the malicious files have been removed. See https://joomla.stackexchange.com/a/180/120 for more information about securing the website once it is fixed.

Magento unsecure_base_url randomly resets to default

I've been working on a Magento site for a few months now. About 2 weeks ago, the site suddenly seemed broken. All the css was gone and I was unable to log into the admin (which was also missing its styles).
I was able to access the database through my host's control panel & found that the unsecure_base_url and secure_base_url were both changed. I had set them to:
mysubdir.mysite.com/
but now they had /magento on the end like this:
mysubdir.mysite.com/magento/
This was the default value upon installation. But since the entire site is in magento, I took it out of this directory and moved it into the web root when I started the project.
I manually changed the values in the database, along with my admin password, which was also not working. About a week later, the same thing happened again. Then a couple days later, it happened again. Then it happened again in the next day and again in the same day after I fixed it.
In the meantime, I've been scouring the server looking for any scripts that could be running that would change these values. I haven't found anything. I looked at every file that had a date matching the time this started & verified with my host that they were legitimate files.
I've also been looking through the magento code, looking for every instance of "core_config_data" to see if I can find any code that sets that value but I haven't found anything yet.
I'm using the community edition. Is there some code in there that resets the base urls after a trial period or something? I've searched but can't find anyone else who's experienced this problem.
I did find some magento cache files that contained mysubdir.mysite.com/magento/. Could it be that it's reverting to cached values? I've flushed the magento cache and cache storage. caching is actually disabled on the site at the moment anyway because it's still in development but it was enabled previously.
Thanks in advance for ANY help, leads, or advice.
If it's being set programmatically via some kind of observer or Magento-configured cron, this is the most probable syntax:
$config->saveConfig('web/unsecure/base_url', 'http://www.example.com/', 'default');
$config->saveConfig('web/secure/base_url', 'https://www.example.com/', 'default');
Knowing this, I'd do a search for this string:
grep -Ri "saveConfig('web/secure/base_url" .
grep -Ri "saveConfig('web/unsecure/base_url" .
I'd start in app/code, and if that turns up nothing, I'd sit through a grep in the Magento root directory.
That will at least rule that out if nothing else.

Sitecore 6.5 Content Delivery Problems (publishing/caching?)

We have a Sitecore 6.5 instance with separate CM and CD servers, each uses it's own core, web and master db's as well.
We are seeing issues when a new version of content is created. The CM Master and Web databases show the correct content in the content editor. After a publish, the Web database on CD shows the correct content in the content editor.
However, the website is showing a mix of correct content and standard values.
Some things I've tried and noticed:
Clearing cache manually as no effect.
No publishing or cache errors in the CD or CM logs
We've reviewed the Scalability Guide to be sure CD and CM are setup correctly
Saving the item in the CD content editor immediately fixes the problem until a new version is created and published on CM
Republishing vs Smart Publish has no affect
The site is correct when viewing the CM version
I'd love to hear anyone's thoughts or questions that might steer me in the right direction.
We finally figured out this issue with some solid help from Sitecore support.
The pages that were "misbehaving" used the Lucene index to locate the Sitecore item and then display information from the item. In our case, the Lucene index was not being updated when the item was published.
Sitecore recommended configuring the HistoryEngine for the web databases on both CD and CM. That fixed the issue.
<Engines.HistoryEngine.Storage>
<obj type="Sitecore.Data.$(database).$(database)HistoryStorage, Sitecore.Kernel">
<param connectionStringName="$(id)" />
<EntryLifeTime>30.00:00:00</EntryLifeTime>
</obj>
</Engines.HistoryEngine.Storage>
<Engines.HistoryEngine.SaveDotNetCallStack>false</Engines.HistoryEngine.SaveDotNetCallStack>
We still have a couple things we can't explain and Sitecore couldn't either
How was this working for other sites on the same instance in the past? What caused the issue to start now?
Why were the pages displaying some of the items' content? Where was that coming from?
Now that I know the fix, I'll have to dig in some more to see if I can figure out these questions.
Hopefully this steers someone else in the right direction.

Resources